Skip to main content

Team Foundation Server 2012: Configure security to access data warehouse

Team Foundation Server gives you a rich set of reporting data available through reporting services and excel reports. If these out-of-the-box reports are not sufficient for you, you can always connect directly to the TFS data warehouse. Microsoft did a great job in improving the data warehouse structure to make it easy to browse through all available info and create your own queries. The easiest way to do this is by using the Analysis services integration in Microsoft Excel. Just follow the wizard and you get all the data you’ll ever need…

image

However there is one extra step you need to do before users can complete this wizard successfully, you must grant these users read access to the databases that make up the data warehouse. You can grant access to the analysis services database, the relational database, or both, depending on what types of reports will be created.

To grant a user or group read access to the analysis services database

  1. On the Start menu, point to All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio. SQL Server Management Studio starts, and the Connect to Server dialog box appears.

  2. In the Server type list, click Analysis Services.

  3. In the Server name box, type the name of the analysis services server for Team Foundation Server, and then click Connect. The Connect to Server dialog box closes.

  4. In Object Explorer, expand the server's Databases folder, then expand the Tfs_Analysis database, and then expand the Roles folder.

  5. Right-click the TfsWarehouseDataReader role, and then click Properties. The Edit Role dialog box appears.

  6. Under Select a page, click Membership, and then click Add. The Select Users or Groups dialog box appears.

  7. Add the user or group, click OK, and then click OK.

To grant a user or group read access to the relational database

  1. On the Start menu, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio. The Connect to Server dialog box appears.

  2. In the Server type list, click Database Engine.

  3. In the Server name box, type the name of the data-tier server for Team Foundation Server, and then click Connect.

  4. In Object Explorer, expand the server's Databases folder, and then expand the Tfs_Warehouse database.

  5. Under the Tfs_Warehouse database, expand the Security folder, then expand the Roles folder, and then expand the Database Roles folder.

  6. Right-click the TfsWarehouseDataReader role, and then click Properties. The Database Role Properties dialog box appears.

  7. Under Select a page, click General, and then click Add. The Select Users or Groups dialog box appears.

  8. Add the user or group, click OK, and then click OK.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more