Microsoft SQL Server Version List

For the bazillionth time, I had to correlate a SQL Server version number (that is, 9.00, 11.0.2000.8, etc.) to what we humans usually use (SQL Server 2005, SQL Server 2012, etc.).

I printed this out and taped it to my desk. Here it is for your use:

RTM (no SP)SP1SP2SP3SP4
↓ SQL Server 2016
     codename ?		CTP3.1
↓ SQL Server 2014
     codename Hekaton SQL14		12.0.2000.812.0.4100.1
or 12.1.4100.1
↓ SQL Server 2012
     codename Denali		11.0.2100.6011.0.3000.0
or 11.1.3000.0		11.0.5058.0
or 11.2.5058.0		11.0.6020.0
or 11.3.6020.0
↓ SQL Server 2008 R2
     codename Kilimanjaro		10.50.1600.110.50.2500.0
or 10.51.2500.0		10.50.4000.0
or 10.52.4000.0		10.50.6000.34
or 10.53.6000.34
↓ SQL Server 2008
     codename Katmai		10.0.1600.2210.0.2531.0
or 10.1.2531.0		10.0.4000.0
or 10.2.4000.0		10.0.5500.0
or 10.3.5500.0		10.0.6000.29
or 10.4.6000.29
↓ SQL Server 2005
     codename Yukon		9.0.1399.069.0.20479.0.30429.0.40359.0.5000
↓ SQL Server 2000
     codename Shiloh		8.0.1948.0.3848.0.5328.0.7608.0.2039
↓ SQL Server 7.0
     codename Sphinx		7.0.6237.0.6997.0.8427.0.9617.0.1063

This came from http://sqlserverbuilds.blogspot.com/, credit where credit is due! This info is also availbe at https://buildnumbers.wordpress.com/sqlserver/.



If you're not sure which version you're using, take a look here: 


Or you can use the following quick & dirty SQL statement:

SELECT @@version

Nice!

Comments

Post a Comment

Popular posts from this blog

Using Reference Aliases

Image
I recently ran across a situation where two different libraries shared identical namespaces and class names. Visual Studio complained anytime I used one of these classes that it was an ambiguous reference. I needed both libraries -- each contained some unique elements -- so I couldn't ditch one or the other. But, as I said, anytime I tried to use a class that was common (again, via the class name and namespace), I received the ambiguous reference error. This was a real problem, so say the least. However, C# provides a way to specify exactly which library (reference) you mean when you use an object that's common to two or more libraries. Simply put, you use an extern alias  statement. The concept is fairly simple: Give the reference an alias (I used the Properties windows for the reference). Add an extern alias statement, putting it before your using statements. Add a using statement, which effectively links a specific object through the extern alias statement to th...
Read more

List of Visual Studio Keyboard Shortcuts

Here's a link to a great list of keyboard shortcuts for Visual Studio: 149 Shortcuts for Visual Studio 2015 (Windows) While there's no need to memorize the list (that's why someone has created a cheat sheet, after all), it certainly doesn't hurt to look over the list from time to time and try to add one more command to your repertoire.
Read more

Quick Example of System.IO.Abstractions Use

I just got on a new project and am trying from the get-go to structure all my code so that it's easily testable. Academically, that is a no-brainer. In practice, though, some chunks of code are more difficult to structure so that they're easily testable. Towards that end, I've been pushing System.IO.Abstractions again. And, to get that going I decided it was time to refresh my examples. In the code below, we see how injecting the file system into the repository ultimately allows us to write testable code. If structured correctly, then our repository requires no subsequent refactoring to run in a unit test environment versus a "real" environment even when dealing with something like the file system. Let's take a look at our code. The Console Application The console application is straightforward. We have a private method (at the bottom) that assembles and returns a mock file system. Next, we perform the following steps: We feed that mock file system...
Read more