Skip to main content

Monitor your Team Foundation Server data volumes

Last week I had to solve a problem for a customer were the disks of their Team Foundation Server environment were filling up. One thing that can help you prevent this kind of problems is the TFS Best Practices Analyzer, which is a part of the Team Foundation Server 2010 Power Tools.

The Best Practices Analyzer can be used to monitor the health of your Team Foundation Server environment. One of the features it has is the ability to obtain usage data about the volume of data stored or accessed in the past 14 days. This includes specific information about database tables that have a tendency to grow large, and may need to be reduced in size.

To run the BPA, select Start -> All Programs -> Microsoft Team Foundation Server 2010 Power Tools -> Best Practice Analyzer.

To run a scan for the first time, click the “select options for a new scan” link. You can name the scan, and select the type of scan you want to perform:

  • Team Foundation Server Complete Health Check
  • Team Foundation Server Framework Health Check
  • Team Foundation Server Warehouse Health Check
  • Team Foundation Build Health Check
  • Visual Studio Lab Management Health Check
  • Sharepoint Products Health Check
  • Team Foundation Server Statistics

Finally, you select the Team Foundation Server you want to run against.

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