Which version of SQL Server is installed?
Every time I want to know which version of SQL Server is installed on a specific environment, I need to go to do some googling to check which name corresponds to the version number I received from my SQL Server. To end this, I’ve created this post as a list primarly for myself but as this is a public blog, I’m also sharing this with everybody else. This list does not contain any SQL Server Express versions yet. Maibe I’ll add them in the future.
To retrieve the version number from your instance of SQL Server, just run the following query.in a query tool like SSMS:
select @@version
This query returns the version number of the current installed SQL Server version.
I hope you’ll find the number in the following list:
|
SQL Server 2008 R2 |
|
|
10.50.1765.0 |
|
|
10.50.1753.0 |
|
|
10.50.1746.0 |
|
|
10.50.1734.0 |
|
|
10.50.1720.0 |
|
|
10.50.1702.0 |
|
|
10.50.1600.1 |
SQL Server 2008 R2 RTM |
|
SQL Server 2008 |
|
|
10.00.4272 |
|
|
10.00.4266 |
|
|
10.00.4000 |
|
|
10.00.2808 |
|
|
10.00.2804 |
|
|
10.00.2799 |
|
|
10.00.2789 |
|
|
10.00.2775 |
|
|
10.00.2766 |
|
|
10.00.2757 |
|
|
10.00.2746 |
|
|
10.00.2734 |
|
|
10.00.2723 |
|
|
10.00.2714 |
|
|
10.00.2710 |
|
|
10.00.2531 |
|
|
10.00.1835 |
|
|
10.00.1828 |
|
|
10.00.1823 |
|
|
10.00.1818 |
|
|
10.00.1812 |
|
|
10.00.1806 |
|
|
10.00.1798 |
|
|
10.00.1787 |
|
|
10.00.1779 |
|
|
10.00.1763 |
|
|
10.00.1600 |
SQL Server 2008 RTM |
|
SQL Server 2005 |
|
|
9.00.5266 |
|
|
9.00.5259 |
|
|
9.00.5254 |
|
|
9.00.5000 |
|
|
9.00.4325 |
|
|
9.00.4317 |
|
|
9.00.4315 |
|
|
9.00.4311 |
|
|
9.00.4309 |
|
|
9.00.4305 |
|
|
9.00.4294 |
|
|
9.00.4285 |
|
|
9.00.4273 |
|
|
9.00.4266 |
|
|
9.00.4230 |
|
|
9.00.4226 |
|
|
9.00.4220 |
|
|
9.00.4211 |
|
|
9.00.4207 |
|
|
9.00.4053 |
|
|
9.00.4035 |
|
|
9.00.3356 |
|
|
9.00.3355 |
|
|
9.00.3330 |
|
|
9.00.3328 |
|
|
9.00.3325 |
|
|
9.00.3315 |
|
|
9.00.3310 |
|
|
9.00.3301 |
SQL Server 2005 SP2 CU11 |
|
9.00.3294 |
|
|
9.00.3282 |
|
|
9.00.3257 |
|
|
9.00.3239 |
|
|
9.00.3233 |
SQL Server 2005 QFE Security Hotfix |
|
9.00.3228 |
|
|
9.00.3215 |
|
|
9.00.3200 |
|
|
9.00.3186 |
|
|
9.00.3175 |
|
|
9.00.3161 |
SQL Server 2005 SP2 CU1 |
|
9.00.3152 |
|
|
9.00.3077 |
|
|
9.00.3054 |
|
|
9.00.3042.01 |
|
|
9.00.3042 |
SQL Server 2005 SP2 |
|
9.00.2047 |
SQL Server 2005 SP1 |
|
9.00.1399 |
SQL Server 2005 RTM |
|
SQL Server 2000 |
|
|
8.00.2039 |
SQL Server 2000 SP4 |
|
8.00.0760 |
SQL Server 2000 SP3 |
|
8.00.0534 |
SQL Server 2000 SP2 |
|
8.00.0384 |
SQL Server 2000 SP1 |
|
8.00.0194 |
SQL Server 2000 RTM |
|
SQL Server 7 |
|
|
7.00.1063 |
SQL Server 7 SP4 |
|
7.00.0961 |
SQL Server 7 SP3 |
|
7.00.0842 |
SQL Server 7 SP2 |
|
7.00.0699 |
SQL Server 7 SP1 |
|
7.00.0623 |
SQL Server 7 RTM |
|
SQL Server 6.5 |
|
|
6.50.416 |
SQL Server 6.5 SP5a |
|
6.50.415 |
SQL Server 6.5 SP5 |
|
6.50.281 |
SQL Server 6.5 SP4 |
|
6.50.258 |
SQL Server 6.5 SP3 |
|
6.50.240 |
SQL Server 6.5 SP2 |
|
6.50.213 |
SQL Server 6.5 SP1 |
|
6.50.201 |
SQL Server 6.5 RTM |



In June this year, I had the opportunity together with 24 other students to follow a full week course organized by Microsoft and
As our team is working in several branches at the customer I’m currently working for, we use aliases to configure our connection string in the web.config of our web- and WCF-services. The advantage of this, is that our connection strings are still working after merging from one to another branch without changing the configs. The only thing we need to do on our development machines, is change the alias to the right SQL server instance.




