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

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more