Skip to main content

Be aware : Team Foundation Server 2015 Upgrade can take a long time

With the release of Team Foundation Server 2015, it’s time to upgrade our existing TFS 2013 environments. One warning before you start, upgrading to TFS 2015 can take a long time(depending on the size of your database), a lot longer than upgrading previous versions. The reason for this is that TFS 2015 includes schema changes to a large number of tables in order to support renaming team projects.

If you want to minimize downtime, it is recommended to use TfsPreUpgrade.exe, a small tool that does the most expensive parts of the work to upgrade to TFS 2015 while your TFS 2013 deployment is still online. TfsPreUpgrade.exe works by creating new copies of the tables most impacted by the schema changes present in TFS 2015 and then migrating data from the original tables to the new copies. As TfsPreUpgrade.exe adds some triggers behind the scenes, it can have a negative impact on performance. So only run it when you will upgrade TFS in the near future.

Remark: TfsPreUpgrade.exe can provide a rough estimate of how long it will take to execute by running the Estimate command.

More information: https://msdn.microsoft.com/en-us/library/vs/alm/tfs/upgrade/pre-upgrade

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

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

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