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

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