Skip to main content

Rolling out TFS 11: Update your SQL Server first

Last week I finally had some time to start migrating our TFS 2010 environment to the TFS 11 beta. The first time I tried to do the migration it failed because I didn’t had the latest updates installed for SQL Server 2008 R2. The installation procedure mentions that you need at least SQL Server 2008 R2 with SP1 and Cumulative Update 1 installed.

So to get everything working, first install SP1: http://www.microsoft.com/download/en/details.aspx?id=26727

Afterwards you can download and install the Cumulative Updates(I think Cumulative Update 4 is the latest version): http://support.microsoft.com/kb/2633146.

Don’t try to mix the order, in that case you’ll end with the following error message(or something similar) during installation:

The version of SQL Server instance MSSQLSERVE does not match the version expected by the SQL SErver update. The installed SQL Server product version is 10.50.1600.1, and the expected SQL Server version is 10.51.2500.0.

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...

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.

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...