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

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

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more