|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
installed SP3 but @@version shows sp2
I install SQL 2005 standard edition SP3 which completed with no errors. When running select @@ version Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) I only have a single instance installled. Installed this: SQLServer2005SP3-KB955706-x86-ENU.exe Am puzzlled. Windows 2003 server 64 bit standard. Thanks scott Hi Scott,
9.00.4035.00 is SQL Server 2005 SP3. "Build 3790: Service Pack 2" refers to your operating system version. Use this to check your SQL Server version: SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition') -- Show quoteHide quoteRubén Garrigós Solid Quality Mentors Blog: http://blogs.solidq.com/es/elrincondeldba Scott escribió: > Hi, > > I install SQL 2005 standard edition SP3 which completed with no errors. > > When running > > select @@ version > > Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 > Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows > NT 5.2 (Build 3790: Service Pack 2) > > I only have a single instance installled. > > Installed this: > > SQLServer2005SP3-KB955706-x86-ENU.exe > > Am puzzlled. > > Windows 2003 server 64 bit standard. > > Thanks > scott > > In SQL Server 2008, the SQL Server service pack level is also included in
the @@VERSION string. For example: Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) The SERVERPROPERTY method Rubén suggested works with this and older versions as well. Show quoteHide quote "Scott" <nospam123@yahoo.co.uk> wrote in message news:OZYvnEKAKHA.1536@TK2MSFTNGP05.phx.gbl... > LOL :-) thank you. >
Other interesting topics
report on indexes on foreign keys
SQL cannot connect to database for OnePoint/MOM/ForeFront all of the sudden??? using profiler to log master.sysprocesses entries ? Best Practices - using params passed to stored procedure Locks and SQLAgent - Generic refresher, Alert Engine Connection server utilizing trusted connection to other SQL Server SQL 2k and autonumbering Exception Access Violation in SQL Log Shipping and extremely large .wrk file Growing log file issue |
|||||||||||||||||||||||