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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more