共用方式為


SQL Server Instance Discovery and Inventory

As with any technical project, defining boundaries is an important step. For a new SQL Server DBA, SQL server instance discovery will allow you to map server names to physical location, application/database dependencies, and SQL Server instance details. If your organization already has an inventory, get a copy to help yourself learn the topology details, architecture patterns, and environment of your organization.

A complete inventory is essential because it enables you to troubleshoot and quickly move to solutions.

SQL Server instance discovery and inventory is a one-time task that will produce a table you can update when significant changes are made.  You can also transfer the information to runbooks or to create new information stores if your organization does not have them already.  Note that it might take some time to complete your discovery, and that proprietary information must be distributed and stored according to the policies of your organization.

Use the information in Table 1. to identify the build numbers for SQL Server versions. 

Table 1. SQL Server Common Build Numbers and Service Packs (As of May-2011)

 SQL Server 2000 (Shiloh)

8.00.194

SQL Server 2000 RTM or MSDE 2.0

8.00.384

SQL Server 2000 SP1

8.00.534

SQL Server 2000 SP2

8.00.701

Hotfix Installer v.1 released

8.00.760

SQL Server 2000 SP3 or SP3a (8.00.766 ssnetlib.dll)

8.00.765

Post SP3 hotfix rollup

8.00.818

(821277)

8.00.977

Update.exe Hotfix Installer Baseline 1 (884856)

8.00.1007

Update.exe Hotfix Installer Baseline 2 (891640)

8.00.2039

SQL Server 2000 SP4

8.00.2040

Post-SP4 AWE fix (899761)

8.00.2187

Post SP4 hotfix rollup with most of the regressions fixed

8.00.2191

Post-SP4 IA64 regression fixed (916950)

8.00.2273

MS08-040 - KB 948111 July 8, 2008

8.00.2282

MS09-004: KB959420 October 29,2008

8.00.2283

Post-SP4 hotfix for MS09-004 (971524)

 SQL Server 2005 (Yukon)

9.00.1399

RTM

9.00.2047

SP1

9.00.3042

SP2 (see 937137 for list of ALL CU & OD patches)

9.00.3152

SP2 Rollup (933097) May 15, 2007

9.00.3161

SP2 CU #1 (935356) April 16, 2007

9.00.3175

SP2 CU #2 (936305) June 18, 2007

9.00.3186

SP2 CU #3 (939537) Aug 20, 2007

9.00.3200

SP2 CU #4 (941450) Oct 15, 2007

9.00.3215

SP2 CU #5 (943656) Dec 17, 2007

9.00.3228

SP2 CU #6 (946608) Feb 18, 2008

9.00.3239

SP2 CU #7 (949095) April 14, 2008

9.00.3257

SP2 CU #8 (951217) June 16, 2008

9.00.3282

SP2 CU #9 (953752) Aug 18, 2008

9.00.3294

SP2 CU #10 (956854) Oct 21, 2008

9.00.3301

SP2 CU #11 (958735) Dec 15, 2008

9.00.3315

SP2 CU #12 (960485) Feb 16, 2009

9.00.3325

SP2 CU #13 (967908) Apr 20, 2009

9.00.3328

SP2 CU #14 (970278) June 15, 2009

9.00.3330

SP2 CU #15 (972510) Aug 17, 2009

9.00.3355

SP2 CU #16 (974647) Oct 19, 2009

9.00.3356

SP2 CU #17 (976952) Dec 21, 2009 - Final

9.00.4035

SP3 RTW (955706) Dec 15, 2008

9.00.4207

SP3 CU #1 (959195) Dec 19, 2008 (CU10 and CU11 rollup)

9.00.4211

SP3 CU #2 (961930) Feb 16, 2009

9.00.4220

SP3 CU #3 (967909) Apr 20, 2009

9.00.4226

SP3 CU #4 (970279) June 15, 2009

9.00.4230

SP3 CU #5 (972511) Aug 17, 2009

9.00.4266

SP3 CU #6 (974648) Oct 19, 2009

9.00.4273

SP3 CU #7 (976951) Dec 21, 2009

9.00.4285

SP3 CU #8 (978915) February 16, 2010

9.00.4294

SP3 CU #9 (980176) April 19, 2010

9.00.4305

SP3 CU #10 (983329) June 21, 2010

9.00.4309

SP3 CU #11 (2258854) Aug 16, 2010

9.00.4311

SP3 CU #12 (2345449) Oct 18, 2010

9.00.4315

SP3 CU #13 (2438344) Dec 20, 2010

9.00.4317

SP3 CU #14 (2489375) Feb 21, 2011

9.00.4325

SP3 CU #15 (2507766) Mar 22 , 2011 – FINAL

9.00.5000

SP4 RTW (PCU4) Dec 16, 2010

9.00.5254

SP4 CU #1 (2464079) Dec 23, 2010

9.00.5259

SP4 CU #2 (2489409) Feb 21, 2010

9.00.5266

SP4 CU #3 (2507769) Mar 22, 2011 - FINAL

 SQL Server 2008 (Katmai)

10.00.1600.22

RTM – Aug 6, 2008

10.00.1763.00

RTM CU #1 (956717) Sept 22, 2008

10.00.1779.00

RTM CU #2 (958186) Nov 19, 2008

10.00.1787.00

RTM CU #3 (960484) Jan 19, 2009

10.00.1798.00

RTM CU #4 (963036) Mar 16, 2009

10.00.1806.00

RTM CU #5 (969531) May 18, 2009

10.00.1812.00

RTM CU #6 (971490) July 20, 2009

10.00.1818.00

RTM CU #7 (973601) Sept 21, 2009

10.00.1823.00

RTM CU #8 (975976) Nov 16, 2009

10.00.1828.00

RTM CU #9 (977444) Jan 18, 2010

10.00.1835.00

RTM CU #10 (979064) March 15, 2010 - Final

10.00.2531.00

SP1 RTW / PCU 1 April, 2009

10.00.2710.00

SP1 CU #1 (969099) April 16, 2009

10.00.2714.00

SP1 CU #2 (970315) May 18, 2009

10.00.2723.00

SP1 CU #3 (971491) July 20, 2009

10.00.2734.00

SP1 CU #4 (973602) Sept 21, 2009

10.00.2746.00

SP1 CU #5 (975977) Nov 16, 2009

10.00.2757.00

SP1 CU #6 (977443) Jan 18, 2010

10.00.2766.00

SP1 CU #7 (979065) Mar 26, 2010

10.00.2775.00

SP1 CU #8 (981702) May 17, 2010

10.00.2789.00

SP1 CU #9 (2083921) July 19, 2010

10.00.2799.00

SP1 CU #10 (2279604) Sept 20, 2010

10.00.2804.00

SP1 CU #11 (2413738) Nov 15, 2010

10.00.2808.00

SP1 CU #12 (2467236) Jan 17. 2011

10.00.2816.00

SP1 CU#13 (2497673) Mar 17, 2011

10.00.4000.00

SP2 RTW / PCU 2 (2285068) Sept 29, 2010

10.00.4266.00

SP2 CU #1 ( 2289254) 

10.00.4272.00

SP2 CU #2 (2467239) Jan 17, 2011

10.00.4279.00

SP2 CU #3 (2498535) Mar 17, 2011

 SQL Server 2008 R2 (Kilimanjaro)

10.50.1600.1

RTM – May 10, 2010

10.50.1702.00

RTM CU #1 (981355) May 18, 2010

10.50.1720.00

RTM CU #2 (2072493) June 21, 2010

10.50.1734.00

RTM CU #3 (2261464) Aug 16, 2010

10.50.1746.00

RTM CU #4 (2345451) Oct 18, 2010

10.50.1753.00

RTM CU #5 (2438347) Dec 20, 2010

10.50.17__.00

RTM CU #6 (2489376) Feb 21, 2011

  Related topics:

 4-part naming

SQL Server provides functionality to reference objects within a database, in another database, or to reference a different instance of SQL Server. This method uses a taxonomy called four-part naming. The four parts that are used to reference a database object in a hierarchy:

For SQL Server 2000:  server.database.owner.object

For SQL Server 2005 and higher:  server.database.schema.object

SQL Server Support Life Cycle

For information about the SQL Server support life cycle, see https://support.microsoft.com/gp/lifeselectindex.