/ MicroSoft SQL Server

SQL Server Builds

Microsoft SQL Server Version List

What version of SQL Server do I have?

This unofficial build chart lists all of the known Service Packs (SP), Cumulative Updates (CU), patches, hotfixes and other builds of MS SQL Server 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5 and 6.0 that have been released.
Useful articles:

Quick summary:

RTM (no SP)SP1SP2SP3SP4
↓ SQL Server 2016
     codename ?		13.0.1601.5



↓ SQL Server 2014
     codename Hekaton SQL14		12.0.2000.812.0.4100.1
or 12.1.4100.1		12.0.5000.0
or 12.2.5000.0
↓ 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
All SQLServer service packs are cumulative, meaning that each new service pack contains all the fixes that are included with previous service packs and any new fixes.
You can comment here. If you know of a hotfix build or KB that we don't have listed here, please use the comments.
Legend:
CTPCommunity Technology Preview (beta release)
RCRelease Candidate
RTMReleased To Manufacturing; It is the original, released build version of the product, i.e. what you get on the DVD or when you download the ISO file from MSDN.
CUCumulative Update; Cumulative updates contain the bug fixes and enhancements–up to that point in time–that have been added since the previous Service Pack release and will be contained in the next service pack release. Installation of the Cumulative Update is similar to the installation of a Service Pack. Cumulative Updates are not fully regression tested.
* Since January 27, 2016: Microsoft recommends ongoing, proactive installation of SQL Server CUs as they become available. SQL Server CUs are certified to the same levels as Service Packs, and should be installed with the same level of confidence.
SPService Pack; much larger collection of hotfixes that have been fully regression tested. In some cases delivers product enhancements.
GDRGeneral Distribution Release; GDR fixes should not contain any of the CU updates.
QFEQuick Fix Engineering; QFE updates include CU fixes.

Microsoft SQL Server 2016 Builds

BuildFile versionKB / DescriptionRelease Date
13.00.2149.02015.130.2149.03164674 Cumulative update 1 (CU1) for SQL Server 2016July 26, 2016 *new
13.00.1711.02015.130.1711.03179258 Processing a partition causes data loss on other partitions after the database is restored in SQL Server 2016 (1200)August 17, 2016 *new
13.00.1708.02015.130.1708.03164398 Critical update for SQL Server 2016 MSVCRT prerequisitesJune 3, 2016
13.00.1601.52015.130.1601.5Microsoft SQL Server 2016 RTMJune 1, 2016
13.00.1400.3612015.130.1400.361Microsoft SQL Server 2016 Release Candidate 3 (RC3)April 15, 2016
13.00.1300.2752015.130.1300.275Microsoft SQL Server 2016 Release Candidate 2 (RC2)April 1, 2016
13.00.1200.2422015.130.1200.242Microsoft SQL Server 2016 Release Candidate 1 (RC1)March 18, 2016
13.00.1100.2882015.130.1100.288Microsoft SQL Server 2016 Release Candidate 0 (RC0)March 7, 2016
13.00.1000.2812015.130.1000.281Microsoft SQL Server 2016 Community Technology Preview 3.3 (CTP3.3)February 3, 2016
13.00.900.732015.130.900.73Microsoft SQL Server 2016 Community Technology Preview 3.2 (CTP3.2)December 16, 2015
13.00.800.112015.130.800.11Microsoft SQL Server 2016 Community Technology Preview 3.1 (CTP3.1)November 30, 2015
13.00.700.1392015.130.700.139Microsoft SQL Server 2016 Community Technology Preview 3.0 (CTP3.0)October 28, 2015
13.00.600.652015.130.600.65Microsoft SQL Server 2016 Community Technology Preview 2.4 (CTP2.4)September 30, 2015
13.00.500.532015.130.500.53Microsoft SQL Server 2016 Community Technology Preview 2.3 (CTP2.3)August 28, 2015
13.00.407.12015.130.407.1Microsoft SQL Server 2016 Community Technology Preview 2.2 (CTP2.2)July 23, 2015
13.00.400.912015.130.400.91Microsoft SQL Server 2016 Community Technology Preview 2.2 (CTP2.2) [withdrawn]July 22, 2015
13.00.300.442015.130.300.444Microsoft SQL Server 2016 Community Technology Preview 2.1 (CTP2.1)June 24, 2015
13.00.200.1722015.130.200.172Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2)May 27, 2015

Microsoft SQL Server 2014 Builds

BuildFile versionKB / DescriptionRelease Date
12.00.55112014.120.5511.03178925 Cumulative update package 1 (CU1) for SQL Server 2014 Service Pack 2August 26, 2016 *new
12.00.50002014.120.5000.0SQL Server 2014 Service Pack 2 (SP2)July 11, 2016 *new
12.00.44682014.120.4468.03174038 Cumulative update package 8 (CU8) for SQL Server 2014 Service Pack 1August 15, 2016 *new
12.00.44632014.120.4463.03174370 A memory leak occurs when you use Azure Storage in SQL Server 2014August 4, 2016 *new
12.00.44592014.120.4459.03162659 Cumulative update package 7 (CU7) for SQL Server 2014 Service Pack 1June 20, 2016
12.00.44572014.120.4457.13167392 REFRESHED Cumulative update package 6 (CU6) for SQL Server 2014 Service Pack 1May 31, 2016
12.00.44492014.120.4449.13144524 DEPRECATED Cumulative update package 6 (CU6) for SQL Server 2014 Service Pack 1April 19, 2016
12.00.44392014.120.4439.13130926 Cumulative update package 5 (CU5) for SQL Server 2014 Service Pack 1February 22, 2016
12.00.44372014.120.4437.03130999 On-demand hotfix update package for SQL Server 2014 Service Pack 1 Cumulative Update 4February 5, 2016
12.00.44362014.120.4436.03106660 Cumulative update package 4 (CU4) for SQL Server 2014 Service Pack 1December 22, 2015
12.00.44332014.120.4433.03119148 FIX: Error 3203 and a SQL Server 2014 backup job can't restart when a network failure occursDecember 9, 2015
12.00.44322014.120.4432.03097972 FIX: Error when your stored procedure calls another stored procedure on linked server in SQL Server 2014November 19, 2015
12.00.44272014.120.4427.243094221 Cumulative update package 3 (CU3) for SQL Server 2014 Service Pack 1October 21, 2015
12.00.44222014.120.4422.03075950 Cumulative update package 2 (CU2) for SQL Server 2014 Service Pack 1August 17, 2015
12.00.44192014.120.4419.0An on-demand hotfix update package is available for SQL Server 2014 SP1July 24, 2015
12.00.44162014.120.4416.03067839 Cumulative update package 1 (CU1) for SQL Server 2014 Service Pack 1June 22, 2015
12.00.42192014.120.4219.0TLS 1.2 support for SQL Server 2014 SP1January 27, 2016
12.00.42132014.120.4213.0MS15-058: Description of the nonsecurity update for SQL Server 2014 Service Pack 1 GDR: July 14, 2015July 14, 2015
12.00.41002014.120.4100.1SQL Server 2014 Service Pack 1 (SP1)May 14, 2015
12.00.40502014.120.4050.0SQL Server 2014 Service Pack 1 (SP1) [withdrawn]April 15, 2015
12.00.25692014.120.2569.03158271 Cumulative update package 14 (CU14) for SQL Server 2014June 20, 2016 *new
12.00.25682014.120.2568.03144517 Cumulative update package 13 (CU13) for SQL Server 2014April 18, 2016
12.00.25642014.120.2564.03130923 Cumulative update package 12 (CU12) for SQL Server 2014February 22, 2016
12.00.25602014.120.2560.03106659 Cumulative update package 11 (CU11) for SQL Server 2014December 22, 2015
12.00.25562014.120.2556.43094220 Cumulative update package 10 (CU10) for SQL Server 2014October 20, 2015
12.00.25532014.120.2553.03075949 Cumulative update package 9 (CU9) for SQL Server 2014August 17, 2015
12.00.25482014.120.2548.0MS15-058: Description of the security update for SQL Server 2014 QFE: July 14, 2015July 14, 2015
12.00.25462014.120.2546.03067836 Cumulative update package 8 (CU8) for SQL Server 2014June 22, 2015
12.00.25062014.120.2506.03063054 Update enables Premium Storage support for Data files on Azure Storage and resolves backup failuresMay 19, 2015
12.00.25052014.120.2505.03052167 FIX: Error 1205 when you execute parallel query that contains outer join operators in SQL Server 2014May 19, 2015
12.00.25042014.120.2504.02999809 FIX: Poor performance when a query contains table joins in SQL Server 2014May 5, 2015
12.00.25042014.120.2504.03058512 FIX: Unpivot Transformation task changes null to zero or empty strings in SSIS 2014May 5, 2015
12.00.24952014.120.2495.03046038 Cumulative update package 7 (CU7) for SQL Server 2014April 23, 2015
12.00.24882014.120.2488.03048751 FIX: Deadlock cannot be resolved automatically when you run a SELECT query that can result in a parallel batch-mode scanApril 1, 2015
12.00.24852014.120.2485.03043788 An on-demand hotfix update package is available for SQL Server 2014March 16, 2015
12.00.24802014.120.2480.03031047 Cumulative update package 6 (CU6) for SQL Server 2014February 16, 2015
12.00.24742014.120.2474.03034679 FIX: AlwaysOn availability groups are reported as NOT SYNCHRONIZINGMay 15, 2015
12.00.24722014.120.2472.03032087 FIX: Cannot show requested dialog after you connect to the latest SQL Database Update V12 (preview) with SQL Server 2014January 28, 2015
12.00.24642014.120.2464.03024815 Large query compilation waits on RESOURCE_SEMAPHORE_QUERY_COMPILE in SQL Server 2014January 5, 2015
12.00.24562014.120.2456.03011055 Cumulative update package 5 (CU5) for SQL Server 2014December 18, 2014
12.00.24362014.120.2436.03014867 FIX: "Remote hardening failure" exception cannot be caught and a potential data loss when you use SQL Server 2014November 27, 2014
12.00.24302014.120.2430.02999197 Cumulative update package 4 (CU4) for SQL Server 2014October 21, 2014
12.00.24232014.120.2423.03007050 FIX: RTDATA_LIST waits when you run natively stored procedures that encounter expected failures in SQL Server 2014October 22, 2014
12.00.24052014.120.2405.02999809 FIX: Poor performance when a query contains table joins in SQL Server 2014September 25, 2014
12.00.24022014.120.2402.02984923 Cumulative update package 3 (CU3) for SQL Server 2014August 18, 2014
12.00.23812014.120.2381.02977316 MS14-044: Description of the security update for SQL Server 2014 (QFE)August 12, 2014
12.00.23702014.120.2370.02967546 Cumulative update package 2 (CU2) for SQL Server 2014June 27, 2014
12.00.23422014.120.2342.02931693 Cumulative update package 1 (CU1) for SQL Server 2014April 21, 2014
12.00.22712014.120.2271.0TLS 1.2 support for SQL Server 2014 RTMJanuary 27, 2016
12.00.22692014.120.2269.03045324 MS15-058: Description of the security update for SQL Server 2014 GDR: July 14, 2015July 14, 2015
12.00.22542014.120.2254.02977315 MS14-044: Description of the security update for SQL Server 2014 (GDR)August 12, 2014
12.00.20002014.120.2000.8SQL Server 2014 RTMApril 1, 2014
12.00.15242014.120.1524.0Microsoft SQL Server 2014 Community Technology Preview 2 (CTP2)October 15, 2013
11.00.91202013.110.9120.0Microsoft SQL Server 2014 Community Technology Preview 1 (CTP1)June 25, 2013

Microsoft SQL Server 2012 Builds

BuildFile versionKB / DescriptionRelease Date
11.00.65402011.110.6540.03165264 Cumulative update package 4 (CU4) for SQL Server 2012 Service Pack 3July 19, 2016 *new
11.00.65372011.110.6537.03152635 Cumulative update package 3 (CU3) for SQL Server 2012 Service Pack 3May 17, 2016
11.00.65232011.110.6523.03137746 Cumulative update package 2 (CU2) for SQL Server 2012 Service Pack 3March 22, 2016
11.00.65182011.110.6518.03123299 Cumulative update package 1 (CU1) for SQL Server 2012 Service Pack 3January 19, 2016
11.00.62162012.110.6216.27TLS 1.2 support for SQL Server 2012 SP3 GDRJanuary 27, 2016
11.00.60202011.110.6020.0SQL Server 2012 Service Pack 3 (SP3)November 23, 2015
11.00.56552011.110.5655.03165266 Cumulative update package 13 (CU13) for SQL Server 2012 Service Pack 2July 19, 2016 *new
11.00.56492011.110.5649.03152637 Cumulative update package 12 (CU12) for SQL Server 2012 Service Pack 2May 16, 2016
11.00.56462011.110.5646.03137745 Cumulative update package 11 (CU11) for SQL Server 2012 Service Pack 2March 22, 2016
11.00.56442011.110.5644.03120313 Cumulative update package 10 (CU10) for SQL Server 2012 Service Pack 2January 20, 2016
11.00.56412011.110.5641.03098512 Cumulative update package 9 (CU9) for SQL Server 2012 Service Pack 2November 18, 2015
11.00.56362011.110.5636.33097636 FIX: Performance decrease when application with connection pooling frequently connects or disconnects in SQL ServerSeptember 22, 2015
11.00.56342011.110.5634.03082561 Cumulative update package 8 (CU8) for SQL Server 2012 Service Pack 2September 21, 2015
11.00.56292011.110.5629.03087872 FIX: Access violations when you use the FileTable feature in SQL Server 2012August 31, 2015
11.00.56232011.110.5623.03072100 Cumulative update package 7 (CU7) for SQL Server 2012 Service Pack 2July 20, 2015
11.00.56132011.110.5613.03045319 MS15-058: Description of the security update for SQL Server 2012 Service Pack 2 QFE: July 14, 2015July 14, 2015
11.00.55922011.110.5592.03052468 Cumulative update package 6 (CU6) for SQL Server 2012 Service Pack 2May 19, 2015
11.00.55822011.110.5582.03037255 Cumulative update package 5 (CU5) for SQL Server 2012 Service Pack 2March 16, 2015
11.00.55712011.110.5571.03034679 FIX: AlwaysOn availability groups are reported as NOT SYNCHRONIZINGMay 15, 2015
11.00.55692011.110.5569.03007556 Cumulative update package 4 (CU4) for SQL Server 2012 Service Pack 2January 20, 2015
11.00.55562011.110.5556.03002049 Cumulative update package 3 (CU3) for SQL Server 2012 Service Pack 2November 17, 2014
11.00.55482011.110.5548.02983175 Cumulative update package 2 (CU2) for SQL Server 2012 Service Pack 2September 15, 2014
11.00.55322011.110.5532.02976982 Cumulative update package 1 (CU1) for SQL Server 2012 Service Pack 2July 24, 2014
11.00.55222011.110.5522.02969896 FIX: Data loss in clustered index occurs when you run online build index in SQL Server 2012 (Hotfix for SQL2012 SP2)June 20, 2014
11.00.53522012.110.5352.0TLS 1.2 support for SQL Server 2012 SP2 GDRJanuary 27, 2016
11.00.53432011.110.5343.03045321 MS15-058: Description of the security update for SQL Server 2012 Service Pack 2 GDR: July 14, 2015July 14, 2015
11.00.50582011.110.5058.0SQL Server 2012 Service Pack 2 (SP2)June 10, 2014
11.00.35132011.110.3513.03045317 MS15-058: Description of the security update for SQL Server 2012 SP1 QFE: July 14, 2015July 14, 2015
11.00.34922011.110.3492.03052476 Cumulative update package 16 (CU16) for SQL Server 2012 Service Pack 1May 18, 2015
11.00.34872011.110.3487.03038001 Cumulative update package 15 (CU15) for SQL Server 2012 Service Pack 1March 16, 2015
11.00.34862011.110.3486.03023636 Cumulative update package 14 (CU14) for SQL Server 2012 Service Pack 1January 19, 2015
11.00.34602011.110.3460.02977325 MS14-044: Description of the security update for SQL Server 2012 Service Pack 1 (QFE)August 12, 2014
11.00.34822011.110.3482.03002044 Cumulative update package 13 (CU13) for SQL Server 2012 Service Pack 1November 17, 2014
11.00.34702011.110.3470.02991533 Cumulative update package 12 (CU12) for SQL Server 2012 Service Pack 1September 15, 2014
11.00.34492011.110.3449.02975396 Cumulative update package 11 (CU11) for SQL Server 2012 Service Pack 1July 21, 2014
11.00.34372011.110.3437.02969896 FIX: Data loss in clustered index occurs when you run online build index in SQL Server 2012 (Hotfix for SQL2012 SP1)June 10, 2014
11.00.34312011.110.3431.02954099 Cumulative update package 10 (CU10) for SQL Server 2012 Service Pack 1May 19, 2014
11.00.34122011.110.3412.02931078 Cumulative update package 9 (CU9) for SQL Server 2012 Service Pack 1March 18, 2014
11.00.34012011.110.3401.02917531 Cumulative update package 8 (CU8) for SQL Server 2012 Service Pack 1January 20, 2014
11.00.33932011.110.3393.02894115 Cumulative update package 7 (CU7) for SQL Server 2012 Service Pack 1November 18, 2013
11.00.33812011.110.3381.02874879 Cumulative update package 6 (CU6) for SQL Server 2012 Service Pack 1September 16, 2013
11.00.33732011.110.3373.02861107 Cumulative update package 5 (CU5) for SQL Server 2012 Service Pack 1July 16, 2013
11.00.33682011.110.3368.02833645 Cumulative update package 4 (CU4) for SQL Server 2012 Service Pack 1May 31, 2013
11.00.33502011.110.3350.02832017 FIX: You can’t create or open SSIS projects or maintenance plans after you apply Cumulative Update 3 for SQL Server 2012 SP1April 17, 2013
11.00.33492011.110.3349.02812412 Cumulative update package 3 (CU3) for SQL Server 2012 Service Pack 1March 18, 2013
11.00.33392011.110.3339.02790947 Cumulative update package 2 (CU2) for SQL Server 2012 Service Pack 1January 25, 2013
11.00.33352011.110.3335.02800050 FIX: Component installation process fails after you install SQL Server 2012 SP1January 14, 2013
11.00.33212011.110.3321.02765331 Cumulative update package 1 (CU1) for SQL Server 2012 Service Pack 1November 20, 2012
11.00.31562011.110.3156.03045318 MS15-058: Description of the security update for SQL Server 2012 SP1 GDR: July 14, 2015July 14, 2015
11.00.31532011.110.3153.02977326 MS14-044: Description of the security update for SQL Server 2012 Service Pack 1 (GDR)August 12, 2014
11.00.31282011.110.3128.02793634 Windows Installer starts repeatedly after you install SQL Server 2012 SP1January 3, 2013
11.00.30002011.110.3000.0SQL Server 2012 Service Pack 1 (SP1)November 6, 2012
11.00.28452011.110.2845.0SQL Server 2012 Service Pack 1 Customer Technology Preview 4 (CTP4)September 20, 2012
11.00.28092011.110.2809.24SQL Server 2012 Service Pack 1 Customer Technology Preview 3 (CTP3)July 5, 2012
11.00.24242011.110.2424.02908007 Cumulative update package 11 (CU11) for SQL Server 2012December 17, 2013
11.00.24202011.110.2420.02891666 Cumulative update package 10 (CU10) for SQL Server 2012October 21, 2013
11.00.24192011.110.2419.02867319 Cumulative update package 9 (CU9) for SQL Server 2012August 21, 2013
11.00.24102011.110.2410.02844205 Cumulative update package 8 (CU8) for SQL Server 2012June 18, 2013
11.00.24052011.110.2405.02823247 Cumulative update package 7 (CU7) for SQL Server 2012April 15, 2013
11.00.24012011.110.2401.02728897 Cumulative update package 6 (CU6) for SQL Server 2012February 18, 2013
11.00.23952011.110.2395.02777772 Cumulative update package 5 (CU5) for SQL Server 2012December 18, 2012
11.00.90002011.110.9000.5Microsoft SQL Server 2012 With Power View For Multidimensional Models Customer Technology Preview (CTP3)November 27, 2012
11.00.23832011.110.2383.02758687 Cumulative update package 4 (CU4) for SQL Server 2012October 18, 2012
11.00.23762011.110.2376.0Microsoft Security Bulletin MS12-070October 9, 2012
11.00.23322011.110.2332.02723749 Cumulative update package 3 (CU3) for SQL Server 2012August 29, 2012
11.00.23252011.110.2325.02703275 Cumulative update package 2 (CU2) for SQL Server 2012June 18, 2012
11.00.23162011.110.2316.02679368 Cumulative update package 1 (CU1) for SQL Server 2012April 12, 2012
11.00.22182011.110.2218.0Microsoft Security Bulletin MS12-070October 9, 2012
11.00.22142011.110.2214.02685308 FIX: SSAS uses only 20 cores in SQL Server 2012 Business IntelligenceApril 6, 2012
11.00.21002011.110.2100.60SQL Server 2012 RTMMarch 6, 2012
11.00.19132011.110.1913.37Microsoft SQL Server 2012 Release Candidate 1 (RC1)December 16, 2011
11.00.17502011.110.1750.32Microsoft SQL Server 2012 Release Candidate 0 (RC0)November 17, 2011
11.00.14402010.110.1440.19Microsoft SQL Server 2012 (codename Denali) Community Technology Preview 3 (CTP3)July 11, 2011
11.00.11032010.110.1103.9Microsoft SQL Server 2012 (codename Denali) Community Technology Preview 1 (CTP1)November 8, 2010

Microsoft SQL Server 2008 R2 Builds

BuildFile versionKB / DescriptionRelease Date
10.50.65422009.100.6542.0Intermittent service terminations occur after you install any SQL Server 2008 or SQL Server 2008 R2 versions from KB3135244March 3, 2016
10.50.65372009.100.6537.0TLS 1.2 support for SQL Server 2008 R2 SP3January 27, 2016
10.50.65292009.100.6529.03045314 MS15-058: Description of the security update for SQL Server 2008 R2 Service Pack 3 QFE: July 14, 2015July 14, 2015
10.50.65252009.100.6525.03033860 An on-demand hotfix update package is available for SQL Server 2008 R2 Service Pack 3 (SP3)February 9, 2015
10.50.62202009.100.6220.03045316 MS15-058: Description of the security update for SQL Server 2008 R2 Service Pack 3 GDR: July 14, 2015July 14, 2015
10.50.60002009.100.6000.0SQL Server 2008 R2 Service Pack 3 (SP3)September 26, 2014
10.50.43432009.100.4343.0TLS 1.2 support for SQL Server 2008 R2 SP2 (IA-64 only)January 27, 2016
10.50.43392009.100.4339.03045312 MS15-058: Description of the security update for SQL Server 2008 R2 Service Pack 2 QFE: July 14, 2015July 14, 2015
10.50.43312009.100.4331.02987585 Restore Log with Standby Mode on an Advanced Format disk may cause a 9004 error in SQL Server 2008 R2 or SQL Server 2012August 27, 2014
10.50.43212009.100.4321.02977319 MS14-044: Description of the security update for SQL Server 2008 R2 Service Pack 2 (QFE)August 12, 2014
10.50.43192009.100.4319.02967540 Cumulative update package 13 (CU13) for SQL Server 2008 R2 Service Pack 2June 30, 2014
10.50.43052009.100.4305.02938478 Cumulative update package 12 (CU12) for SQL Server 2008 R2 Service Pack 2April 21, 2014
10.50.43022009.100.4302.02926028 Cumulative update package 11 (CU11) for SQL Server 2008 R2 Service Pack 2February 18, 2014
10.50.42972009.100.4297.02908087 Cumulative update package 10 (CU10) for SQL Server 2008 R2 Service Pack 2December 16, 2013
10.50.42952009.100.4295.02887606 Cumulative update package 9 (CU9) for SQL Server 2008 R2 Service Pack 2October 29, 2013
10.50.42902009.100.4290.02871401 Cumulative update package 8 (CU8) for SQL Server 2008 R2 Service Pack 2August 30, 2013
10.50.42862009.100.4286.02844090 Cumulative update package 7 (CU7) for SQL Server 2008 R2 Service Pack 2June 17, 2013
10.50.42852009.100.4285.02830140 Cumulative update package 6 (CU6) for SQL Server 2008 R2 Service Pack 2 (updated)June 13, 2013
10.50.42792009.100.4279.02830140 Cumulative update package 6 (CU6) for SQL Server 2008 R2 Service Pack 2 (replaced)April 15, 2013
10.50.42762009.100.4276.02797460 Cumulative update package 5 (CU5) for SQL Server 2008 R2 Service Pack 2February 18, 2013
10.50.42702009.100.4270.02777358 Cumulative update package 4 (CU4) for SQL Server 2008 R2 Service Pack 2December 17, 2012
10.50.42662009.100.4266.02754552 Cumulative update package 3 (CU3) for SQL Server 2008 R2 Service Pack 2October 15, 2012
10.50.42632009.100.4263.02740411 Cumulative update package 2 (CU2) for SQL Server 2008 R2 Service Pack 2August 29, 2012
10.50.42602009.100.4260.02720425 Cumulative update package 1 (CU1) for SQL Server 2008 R2 Service Pack 2August 1, 2012
10.50.40462009.100.4046.0TLS 1.2 support for SQL Server 2008 R2 SP2 GDR (IA-64 only)January 27, 2016
10.50.40422009.100.4042.03045313 MS15-058: MS15-058: Description of the security update for SQL Server 2008 R2 Service Pack 2 GDR: July 14, 2015July 14, 2015
10.50.40332009.100.4033.02977320 MS14-044: Description of the security update for SQL Server 2008 R2 Service Pack 2 (GDR)August 12, 2014
10.50.40002009.100.4000.0SQL Server 2008 R2 Service Pack 2 (SP2)July 26, 2012
10.50.37202009.100.3720.0SQL Server 2008 R2 Service Pack 2 Community Technology Preview (CTP)May 13, 2012
10.50.28812009.100.2881.02868244 An on-demand hotfix update package for SQL Server 2008 R2 Service Pack 1August 12, 2013
10.50.28762009.100.2876.02855792 Cumulative update package 13 (CU13) for SQL Server 2008 R2 Service Pack 1June 17, 2013
10.50.28752009.100.2875.02828727 Cumulative update package 12 (CU12) for SQL Server 2008 R2 Service Pack 1 (updated)June 13, 2013
10.50.28742009.100.2874.02828727 Cumulative update package 12 (CU12) for SQL Server 2008 R2 Service Pack 1 (replaced)April 15, 2013
10.50.28612009.100.2861.0Microsoft Security Bulletin MS12-070October 9, 2012
10.50.28692009.100.2869.02812683 Cumulative update package 11 (CU11) for SQL Server 2008 R2 Service Pack 1February 18, 2013
10.50.28682009.100.2868.02783135 Cumulative update package 10 (CU10) for SQL Server 2008 R2 Service Pack 1December 17, 2012
10.50.28662009.100.2866.02756574 Cumulative update package 9 (CU9) for SQL Server 2008 R2 Service Pack 1November 6, 2012
10.50.28612009.100.2861.02716439 MS12-070: Description of the security update for SQL Server 2008 R2 Service Pack 1 QFE: October 9, 2012October 9, 2012
10.50.28222009.100.2822.02723743 Cumulative update package 8 (CU8) for SQL Server 2008 R2 Service Pack 1August 29, 2012
10.50.28172009.100.2817.02703282 Cumulative update package 7 (CU7) for SQL Server 2008 R2 Service Pack 1June 18, 2012
10.50.28112009.100.2811.02679367 Cumulative update package 6 (CU6) for SQL Server 2008 R2 Service Pack 1April 16, 2012
10.50.28072009.100.2807.02675522 FIX: Access violation when you run DML statements against a table that has partitioned indexes in SQL Server 2008 R2March 12, 2012
10.50.28062009.100.2806.02659694 Cumulative update package 5 (CU5) for SQL Server 2008 R2 Service Pack 1February 22, 2012
10.50.27992009.100.2799.02633357 FIX: "Non-yielding Scheduler" error might occur when you run a query that uses the CHARINDEX function in SQL Server 2008 R2February 22, 2012
10.50.27962009.100.2796.02633146 Cumulative update package 4 (CU4) for SQL Server 2008 R2 Service Pack 1December 20, 2011
10.50.27892009.100.2789.02591748 Cumulative update package 3 (CU3) for SQL Server 2008 R2 Service Pack 1October 17, 2011
10.50.27762009.100.2776.02606883 FIX: Slow performance when an AFTER trigger runs on a partitioned table in SQL Server 2008 R2October 18, 2011
10.50.27722009.100.2772.02567714 Cumulative update package 2 (CU2) for SQL Server 2008 R2 Service Pack 1August 15, 2011
10.50.27692009.100.2769.02544793 Cumulative update package 1 (CU1) for SQL Server 2008 R2 Service Pack 1July 18, 2011
10.50.25502009.100.2550.0Microsoft Security Bulletin MS12-070October 9, 2012
10.50.25002009.100.2500.0SQL Server 2008 R2 Service Pack 1 (SP1)July 11, 2011
10.50.18172009.100.1817.02703280 Cumulative update package 14 (CU14) for SQL Server 2008 R2June 18, 2012
10.50.18152009.100.1815.02679366 Cumulative update package 13 (CU13) for SQL Server 2008 R2April 17, 2012
10.50.18102009.100.1810.02659692 Cumulative update package 12 (CU12) for SQL Server 2008 R2February 21, 2012
10.50.18092009.100.1809.02633145 Cumulative update package 11 (CU11) for SQL Server 2008 R2January 9, 2012
10.50.18072009.100.1807.02591746 Cumulative update package 10 (CU10) for SQL Server 2008 R2October 19, 2011
10.50.18042009.100.1804.02567713 Cumulative update package 9 (CU9) for SQL Server 2008 R2August 16, 2011
10.50.18002009.100.1800.02574699 FIX: Database data files might be incorrectly marked as sparse in SQL Server 2008 R2 or in SQL Server 2008 even when the physical files are marked as not sparse in the file systemOctober 18, 2011
10.50.17972009.100.1797.02534352 Cumulative update package 8 (CU8) for SQL Server 2008 R2June 20, 2011
10.50.17902009.100.1790.02494086 MS11-049: Description of the security update for SQL Server 2008 R2 QFE: June 14, 2011June 17, 2011
10.50.17772009.100.1777.02507770 Cumulative update package 7 (CU7) for SQL Server 2008 R2June 16, 2011
10.50.17692009.100.1769.02520808 FIX: Non-yielding scheduler error when you run a query that uses a TVP in SQL Server 2008 or in SQL Server 2008 R2 if SQL Profiler or SQL Server Extended Events is usedApril 18, 2011
10.50.17652009.100.1765.02489376 Cumulative update package 6 (CU6) for SQL Server 2008 R2February 21, 2011
10.50.17532009.100.1753.02438347 Cumulative update package 5 (CU5) for SQL Server 2008 R2December 23, 2010
10.50.17462009.100.1746.02345451 Cumulative update package 4 (CU4) for SQL Server 2008 R2October 18, 2010
10.50.17342009.100.1734.02261464 Cumulative update package 3 (CU3) for SQL Server 2008 R2August 20, 2010
10.50.17202009.100.1720.02072493 Cumulative update package 2 (CU2) for SQL Server 2008 R2June 25, 2010
10.50.17022009.100.1702.0981355 Cumulative update package 1 (CU1) for SQL Server 2008 R2May 18, 2010
10.50.16172009.100.1617.02494088 MS11-049: Description of the security update for SQL Server 2008 R2 GDR: June 14, 2011June 14, 2011
10.50.16002009.100.1600.1SQL Server 2008 R2 RTMApril 21, 2010
10.50.13522009.100.1352.12Microsoft SQL Server 2008 R2 November Community Technology Preview (CTP)November 12, 2009
10.50.10922009.100.1092.20Microsoft SQL Server 2008 R2 August Community Technology Preview (CTP)June 30, 2009

Microsoft SQL Server 2008 Builds

BuildFile versionKB / DescriptionRelease Date
10.00.65472007.100.6547.0Intermittent service terminations occur after you install any SQL Server 2008 or SQL Server 2008 R2 versions from KB3135244March 3, 2016
10.00.65432007.100.6543.0TLS 1.2 support for SQL Server 2008 SP4January 27, 2016
10.00.65352007.100.6535.03045308 MS15-058: Description of the security update for SQL Server 2008 Service Pack 4 QFE: July 14, 2015July 14, 2015
10.00.65262007.100.6526.03034373 An on-demand hotfix update package is available for SQL Server 2008 Service Pack 4 (SP4)February 9, 2015
10.00.62412007.100.6241.03045311 MS15-058: Description of the security update for SQL Server 2008 Service Pack 4 GDR: July 14, 2015July 14, 2015
10.00.60002007.100.6000.0SQL Server 2008 Service Pack 4 (SP4)September 30, 2014
10.00.58942007.100.5894.0TLS 1.2 support for SQL Server 2008 SP3 (IA-64 only)January 27, 2016
10.00.58902007.100.5890.03045303 MS15-058: Description of the security update for SQL Server 2008 Service Pack 3 QFE: July 14, 2015July 14, 2015
10.00.58692007.100.5869.02977322 MS14-044: Description of the security update for SQL Server 2008 SP3 (QFE)August 12, 2014
10.00.58672007.100.5867.02877204 FIX: Error 8985 when you run the "dbcc shrinkfile" statement by using the logical name of a file in SQL Server 2008 R2 or SQL Server 2008July 2, 2014
10.00.58612007.100.5861.02958696 Cumulative update package 17 (CU17) for SQL Server 2008 Service Pack 3May 19, 2014
10.00.58522007.100.5852.02936421 Cumulative update package 16 (CU16) for SQL Server 2008 Service Pack 3March 17, 2014
10.00.58502007.100.5850.02923520 Cumulative update package 15 (CU15) for SQL Server 2008 Service Pack 3January 20, 2014
10.00.58482007.100.5848.02893410 Cumulative update package 14 (CU14) for SQL Server 2008 Service Pack 3November 18, 2013
10.00.58462007.100.5846.02880350 Cumulative update package 13 (CU13) for SQL Server 2008 Service Pack 3September 16, 2013
10.00.58442007.100.5844.02863205 Cumulative update package 12 (CU12) for SQL Server 2008 Service Pack 3July 16, 2013
10.00.58412007.100.5841.02834048 Cumulative update package 11 (CU11) for SQL Server 2008 Service Pack 3 (updated)June 13, 2013
10.00.58402007.100.5840.02834048 Cumulative update package 11 (CU11) for SQL Server 2008 Service Pack 3 (replaced)May 20, 2013
10.00.58352007.100.5835.02814783 Cumulative update package 10 (CU10) for SQL Server 2008 Service Pack 3March 18, 2013
10.00.58292007.100.5829.02799883 Cumulative update package 9 (CU9) for SQL Server 2008 Service Pack 3January 23, 2013
10.00.58282007.100.5828.02771833 Cumulative update package 8 (CU8) for SQL Server 2008 Service Pack 3November 19, 2012
10.00.58262007.100.5826.02716435 Microsoft Security Bulletin MS12-070October 9, 2012
10.00.57942007.100.5794.02738350 Cumulative update package 7 (CU7) for SQL Server 2008 Service Pack 3September 21, 2012
10.00.57882007.100.5788.02715953 Cumulative update package 6 (CU6) for SQL Server 2008 Service Pack 3July 16, 2012
10.00.57852007.100.5785.02696626 Cumulative update package 5 (CU5) for SQL Server 2008 Service Pack 3May 19, 2012
10.00.57752007.100.5775.02673383 Cumulative update package 4 (CU4) for SQL Server 2008 Service Pack 3March 20, 2012
10.00.57702007.100.5770.02648098 Cumulative update package 3 (CU3) for SQL Server 2008 Service Pack 3January 16, 2012
10.00.57682007.100.5768.02633143 Cumulative update package 2 (CU2) for SQL Server 2008 Service Pack 3November 22, 2011
10.00.57662007.100.5766.02617146 Cumulative update package 1 (CU1) for SQL Server 2008 Service Pack 3October 18, 2011
10.00.55442007.100.5544.0TLS 1.2 support for SQL Server 2008 SP3 GDR (IA-64 only)January 27, 2016
10.00.55382007.100.5538.03045305 MS15-058: Description of the security update for SQL Server 2008 Service Pack 3 GDR: July 14, 2015July 14, 2015
10.00.55202007.100.5520.02977321 MS14-044: Description of the security update for SQL Server 2008 SP3 (GDR)August 12, 2014
10.00.55122007.100.5512.0Microsoft Security Bulletin MS12-070October 9, 2012
10.00.55002007.100.5500.0SQL Server 2008 Service Pack 3 (SP3)October 6, 2011
10.00.54162007.100.5416.0SQL Server 2008 Service Pack 3 CTPAugust 22, 2011
10.00.43712007.100.4371.0Microsoft Security Bulletin MS12-070October 9, 2012
10.00.43332007.100.4333.02715951 Cumulative update package 11 (CU11) for SQL Server 2008 Service Pack 2July 16, 2012
10.00.43322007.100.4332.02696625 Cumulative update package 10 (CU10) for SQL Server 2008 Service Pack 2May 20, 2012
10.00.43302007.100.4330.02673382 Cumulative update package 9 (CU9) for SQL Server 2008 Service Pack 2March 19, 2012
10.00.43262007.100.4326.02648096 Cumulative update package 8 (CU8) for SQL Server 2008 Service Pack 2January 30, 2012
10.00.43232007.100.4323.02617148 Cumulative update package 7 (CU7) for SQL Server 2008 Service Pack 2November 21, 2011
10.00.43212007.100.4321.02582285 Cumulative update package 6 (CU6) for SQL Server 2008 Service Pack 2September 20, 2011
10.00.43162007.100.4316.02555408 Cumulative update package 5 (CU5) for SQL Server 2008 Service Pack 2July 18, 2011
10.00.42852007.100.4285.02527180 Cumulative update package 4 (CU4) for SQL Server 2008 Service Pack 2May 16, 2011
10.00.42792007.100.4279.02498535 Cumulative update package 3 (CU3) for SQL Server 2008 Service Pack 2March 11, 2011
10.00.42722007.100.4272.02467239 Cumulative update package 2 (CU2) for SQL Server 2008 Service Pack 2February 10, 2011
10.00.42662007.100.4266.02289254 Cumulative update package 1 (CU1) for SQL Server 2008 Service Pack 2November 15, 2010
10.00.40672007.100.4067.0Microsoft Security Bulletin MS12-070October 9, 2012
10.00.40642007.100.4064.02494089 MS11-049: Description of the security update for SQL Server 2008 Service Pack 2 GDR: June 14, 2011June 14, 2011
10.00.40002007.100.4000.0SQL Server 2008 Service Pack 2 (SP2)September 29, 2010
10.00.37982007.100.3798.0SQL Server 2008 Service Pack 2 CTPJuly 7, 2010
10.00.28502007.100.2850.02582282 Cumulative update package 16 (CU16) for SQL Server 2008 Service Pack 1September 19, 2011
10.00.28472007.100.2847.02555406 Cumulative update package 15 (CU15) for SQL Server 2008 Service Pack 1July 18, 2011
10.00.28412007.100.2841.02494100 MS11-049: Description of the security update for SQL Server 2008 Service Pack 1 QFE: June 14, 2011June 14, 2011
10.00.28212007.100.2821.02527187 Cumulative update package 14 (CU14) for SQL Server 2008 Service Pack 1May 16, 2011
10.00.28162007.100.2816.02497673 Cumulative update package 13 (CU13) for SQL Server 2008 Service Pack 1March 22, 2011
10.00.28082007.100.2808.02467236 Cumulative update package 12 (CU12) for SQL Server 2008 Service Pack 1February 10, 2011
10.00.28042007.100.2804.02413738 Cumulative update package 11 (CU11) for SQL Server 2008 Service Pack 1November 15, 2010
10.00.27992007.100.2799.02279604 Cumulative update package 10 (CU10) for SQL Server 2008 Service Pack 1September 21, 2010
10.00.27892007.100.2789.02083921 Cumulative update package 9 (CU9) for SQL Server 2008 Service Pack 1July 21, 2010
10.00.27872007.100.2787.02231277 FIX: The Reporting Services service stops unexpectedly after you apply SQL Server 2008 SP1 CU 7 or CU8July 30, 2010
10.00.27752007.100.2775.0981702 Cumulative update package 8 (CU8) for SQL Server 2008 Service Pack 1May 17, 2010
10.00.27662007.100.2766.0979065 Cumulative update package 7 (CU7) for SQL Server 2008 Service Pack 1March 26, 2010
10.00.27572007.100.2757.0977443 Cumulative update package 6 (CU6) for SQL Server 2008 Service Pack 1January 18, 2010
10.00.27462007.100.2746.0975977 Cumulative update package 5 (CU5) for SQL Server 2008 Service Pack 1November 16, 2009
10.00.27402007.100.2740.0976761 FIX: Error message when you perform a rolling upgrade in a SQL Server 2008 cluster : "18401, Login failed for user SQLTEST\AgentService. Reason: Server is in script upgrade mode. Only administrator can connect at this time.[SQLState 42000]"November 24, 2009
10.00.27342007.100.2734.0973602 Cumulative update package 4 (CU4) for SQL Server 2008 Service Pack 1September 22, 2009
10.00.27232007.100.2723.0971491 Cumulative update package 3 (CU3) for SQL Server 2008 Service Pack 1July 21, 2009
10.00.27142007.100.2714.0970315 Cumulative update package 2 (CU2) for SQL Server 2008 Service Pack 1May 18, 2009
10.00.27122007.100.2712.0970507 FIX: Error message in SQL Server 2008 when you run an INSERT SELECT statement on a table: "Violation of PRIMARY KEY constraint '<PrimaryKey>'. Cannot insert duplicate key in object '<TableName>'"July 21, 2009
10.00.27102007.100.2710.0969099 Cumulative update package 1 (CU1) for SQL Server 2008 Service Pack 1April 16, 2009
10.00.25732007.100.2573.02494096 MS11-049: Description of the security update for SQL Server 2008 Service Pack 1 GDR: June 14, 2011June 14, 2011
10.00.25312007.100.2531.0SQL Server 2008 Service Pack 1 (SP1)April 7, 2009
10.00.25202007.100.2520.0SQL Server 2008 Service Pack 1 - CTPFebruary 23, 2009
10.00.18352007.100.1835.0979064 Cumulative update package 10 (CU10) for SQL Server 2008March 15, 2010
10.00.18282007.100.1828.0977444 Cumulative update package 9 (CU9) for SQL Server 2008January 18, 2010
10.00.18232007.100.1823.0975976 Cumulative update package 8 (CU8) for SQL Server 2008November 16, 2009
10.00.18182007.100.1818.0973601 Cumulative update package 7 (CU7) for SQL Server 2008September 21, 2009
10.00.18122007.100.1812.0971490 Cumulative update package 6 (CU6) for SQL Server 2008July 21, 2009
10.00.18062007.100.1806.0969531 Cumulative update package 5 (CU5) for SQL Server 2008May 18, 2009
10.00.17982007.100.1798.0963036 Cumulative update package 4 (CU4) for SQL Server 2008March 17, 2009
10.00.17872007.100.1787.0960484 Cumulative update package 3 (CU3) for SQL Server 2008January 19, 2009
10.00.17792007.100.1779.0958186 Cumulative update package 2 (CU2) for SQL Server 2008November 19, 2008
10.00.17712007.100.1771.0958611 FIX: You may receive incorrect results when you run a query that references three or more tables in the FROM clause in SQL Server 2008October 29, 2008
10.00.17632007.100.1763.0956717 Cumulative update package 1 (CU1) for SQL Server 2008October 28, 2008
10.00.17502007.100.1750.0956718 FIX: A MERGE statement may not enforce a foreign key constraint when the statement updates a unique key column that is not part of a clustering key that has a single row as the update source in SQL Server 2008August 25, 2008
10.00.16002007.100.1600.22SQL Server 2008 RTMAugust 7, 2008
10.00.14422007.100.1442.32Microsoft SQL Server 2008 RC0June 5, 2008
10.00.13002007.100.1300.13Microsoft SQL Server 2008 CTP, February 2008February 19, 2008
10.00.10752007.100.1075.23Microsoft SQL Server 2008 CTP, November 2007November 18, 2007
10.00.10492007.100.1049.14SQL Server 2008 CTP, July 2007July 31, 2007
10.00.10192007.100.1019.17SQL Server 2008 CTP, June 2007May 21, 2007

SQL Server Monitoring

Problem
As you know SQL Server runs using a bunch of different services in order for it to operate.  These can be monitored, started and stopped using SQL Server Configuration Manager or Windows Services, but this is not always the most convenient way of checking the services.  Is there any way this can be done within SQL Server Management Studio?  In this tip we take a look at a undocumented stored procedure that will allow you to do this.
Solution
To check the SQL Server services or any other service status using SSMS you can execute the extended stored procedure xp_servicecontrol.  This is un documented extended stored procedure.
Syntax
EXEC xp_servicecontrol N'Querystat|Start|Stop',N'Service Name' 

QueryState 
Use this command to check the Services status 
whether service is running or stopped
Start
Use this command to start the service
Stop
use this command to stop the service

Examples

--See below example to check the status of SQL Services
EXEC xp_servicecontrol N'querystate',N'MSSQLServer'
EXEC xp_servicecontrol N'querystate',N'SQLServerAGENT'
EXEC xp_servicecontrol N'querystate',N'msdtc'
EXEC xp_servicecontrol N'querystate',N'sqlbrowser'
EXEC xp_servicecontrol N'querystate',N'MSSQLServerOLAPService'
EXEC xp_servicecontrol N'querystate',N'ReportServer'
--See below example to start/stop service using SSMS
EXEC xp_servicecontrol N'stop',N'SQLServerAGENT'
EXEC xp_servicecontrol N'start',N'SQLServerAGENT'
--See below example to check non-SQL Service
EXEC xp_servicecontrol querystate, DHCPServer

To run this on multiple servers you can use SQLCMD as shown below or you can use Central Management Servers.

Step 1 Create "MyScript.sql" file using the below T-SQL:

set nocount on
CREATE TABLE #ServicesStatus
( 
myid int identity(1,1),
serverName nvarchar(100) default @@serverName,
serviceName varchar(100),
Status varchar(50),
checkdatetime datetime default (getdate())
)
INSERT #ServicesStatus (Status)
EXEC xp_servicecontrol N'QUERYSTATE',N'MSSQLServer'
update #ServicesStatus set serviceName = 'MSSQLServer' where myid = @@identity
INSERT #ServicesStatus (Status)
EXEC xp_servicecontrol N'QUERYSTATE',N'SQLServerAGENT'
update #ServicesStatus set serviceName = 'SQLServerAGENT' where myid = @@identity
INSERT #ServicesStatus (Status)
EXEC xp_servicecontrol N'QUERYSTATE',N'msdtc';
update #ServicesStatus set serviceName = 'msdtc' where myid = @@identity;
INSERT #ServicesStatus (Status)
EXEC xp_servicecontrol N'QUERYSTATE',N'sqlbrowser'
update #ServicesStatus set serviceName = 'sqlbrowser' where myid = @@identity
select * from #ServicesStatus 
select char(13)
select char(13)
drop table #ServicesStatus

Step 2 Create a Windows batch file and save it with .bat extension. Add the list of server names you want to check as shown below
  
sqlcmd -SServerName1 -E -dtempdb -iMyScript.sql -W >>sqlServicesStatus.txt
sqlcmd -SServerName2 -E -dtempdb -iMyScript.sql -W >>sqlServicesStatus.txt
sqlcmd -SServerName3 -E -dtempdb -iMyScript.sql -W >>sqlServicesStatus.txt
sqlcmd -SServerName4 -E -dtempdb -iMyScript.sql -W >>sqlServicesStatus.txt
sqlcmd -SServerName5 -E -dtempdb -iMyScript.sql -W >>sqlServicesStatus.txt

Step 3 Execute the batch file and then open "sqlServicesStatus.txt" to see the status for all services that were checked.

FIX: Replication Log Reader Agent fails with "18773" and "18805" error messages if you set the 'large value types out of row' table option to ON for the publication article table

FIX: Replication Log Reader Agent fails with "18773" and "18805" error messages if you set the 'large value types out of row' table option to ON for the publication article table

Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) or Microsoft SQL Server 2012 fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) or Microsoft SQL Server 2012 update release.
SYMPTOMS
Consider the following scenario:
  • You have a table that is used as a publication article in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012.
  • You set the 'large value types out of row' table option to ON for the table.
  • You run a BULK INSERT command to import a data file into the table.
In this scenario, when the Replication Log Reader Agent tries to transfer transactions from the publisher to distributors, the synchonization might fail, and you may receive the following error messages:
Status: 0, code: 18773, text: 'Could not locate text information records for column # during command construction.'.

Status: 0, code: 18805, text: 'The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {00000017:000001d3:0029}. Back up the publication database and contact Customer Support Services.'
CAUSE
This issue occurs because the BULK INSERT command does not generate a certain transaction log record that is only for replication

Update Job owner for all SQL Agent jobs


DECLARE @name_holder VARCHAR(1000)
DECLARE My_Cursor CURSOR
FOR
SELECT [name]  FROM msdb..sysjobs
OPEN My_Cursor
FETCH NEXT FROM My_Cursor INTO @name_holder
WHILE (@@FETCH_STATUS <> -1)
BEGIN
exec msdb..sp_update_job
        @job_name = @name_holder,
        @owner_login_name = 'sa'
FETCH NEXT FROM My_Cursor INTO @name_holder
END
CLOSE My_Cursor
DEALLOCATE My_Cursor

Change Maintenance Plan Owner, Change SSIS Package Owner


If you're used to administering your SQL Servers using Windows Authentication, one side effect is that you'll end up owning a lot of databases, jobs, plans and packages. Sometime this has undesirable effects such as a job or package not working properly. But it's not always obvious how you can change the owner of a package once it's created. Note that it is slightly different for each version of SQL Server.

SQL Server 2008 Maintenance Plan or SSIS Package

--change the owner of a SQL Server 2008 Maintenance Plan or SSIS Package
UPDATE [msdb].[dbo].[sysssispackages]
SET [ownersid] = 0x01 --sa user
WHERE [name] = 'YOUR_MAINT_PLAN_OR_PACKAGE'

SQL Server 2005 Maintenance Plan or SSIS Package

--change the owner of a SQL Server 2005 Maintenance Plan or SSIS Package
UPDATE [msdb].[dbo].[sysdtspackages90]
SET [ownersid] = 0x01 --sa user
WHERE [name] = 'YOUR_MAINT_PLAN_OR_PACKAGE'

SQL Server 2000 Maintenance Plan

--change the owner of a SQL Server 2000 Maintenance Plan
UPDATE [msdb].[dbo].[sysdbmaintplans]
SET [owner] = 'sa'
WHERE [plan_name] = 'YOUR_MAINT_PLAN'

SQL Server 2000 DTS package

--change the owner of a SQL Server 2000 DTS package
--note you need to update the owner column as well
UPDATE [msdb].[dbo].[sysdtspackages]
SET [owner] = 'sa',
 [owner_sid] = 0x01 --sa user
WHERE [name] = 'YOUR_DTS_PACKAGE'
Before I learned this trick, I would literally delete and recreate the package when logged in as SA just to get the package under the proper owner. Otherwise, every time you edit the plan, the job owner will change to match the plan owner which could cause the job to fail.

SQL Job owner issue

select s.name,l.name
 from  msdb..sysjobs s
 left join master.sys.syslogins l on s.owner_sid = l.sid

 select s.name,l.name
from msdb..sysssispackages s
 left join master.sys.syslogins l on s.ownersid = l.sid

 SELECT  s.name ,
        SUSER_SNAME(s.owner_sid) AS owner
FROM    msdb..sysjobs s
ORDER BY name

Common Language Runtime (CLR)

The Common Language Runtime (CLR) is the heart of the Microsoft .NET Framework and provides the execution environment for all .NET Framework code. Code that runs within the CLR is referred to as managed code. The CLR provides various functions and services required for program execution, including just-in-time (JIT) compilation, allocating and managing memory, enforcing type safety, exception handling, thread management, and security.
With the CLR hosted in Microsoft SQL Server (called CLR integration), you can author stored procedures, triggers, user-defined functions, user-defined types, and user-defined aggregates in managed code. Developers use compiled OO languages like C# or Visual Basic .NET to write code and to have the code executed as if it were a T-SQL procedure, function, or trigger. Because managed code compiles to native code prior to execution, you can achieve significant performance increases in some scenarios.
Managed code uses Code Access Security (CAS), code links, and application domains to prevent assemblies from performing certain operations. SQL Server 2005, SQL Server 2008, and SQL Server 2012 uses CAS to help secure the managed code and prevent compromise of the operating system or database server.

Enable CLR in SQL Server

In SQL Server 2005, SQL Server 2008, and SQL Server 2012, the Common Language Runtime (CLR) is off by default. In an effort to improve security, Microsoft has turned many features "off by default". This is a big change from the old policy of turning every feature on so that developers weren't discouraged from using the feature due to difficulties in getting the feature to work.

EXEC sp_configure 'show advanced options', '1'
Go

Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.


Reconfigure
Go

Command(s) completed successfully.


EXEC sp_configure 'clr enabled', '1'
Go

Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.


Reconfigure
Go

Command(s) completed successfully.


EXEC sp_configure 'show advanced options', '0'
Go

Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.


Reconfigure
Go

Command(s) completed successfully.
Subscribe to: Posts (Atom)