MS SQL2005 Updata from SP1 to SP2 Fail

Windows 2003 SP2 Updata MS SQL 2005 from SP1 to SP2 fail.

Hotfix_5.log

07/31/2007 23:15:32.745 ================================================================================
{..........................................

.........................................

........................................}
07/31/2007 23:15:54.236
07/31/2007 23:15:54.246 Product Enumeration Results:
07/31/2007 23:15:54.246 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSqlxml4.inf
07/31/2007 23:15:54.246 baselinebuild = 1399
07/31/2007 23:15:54.246 build = 3042
07/31/2007 23:15:54.246 description = SQLXML4
07/31/2007 23:15:54.256 details = Service Pack for Microsoft SQLXML 4.0.
07/31/2007 23:15:54.256 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.256 kbarticle = KB921896
07/31/2007 23:15:54.256 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.266 lcid = 1033
07/31/2007 23:15:54.266 legalproductname = SQLXML4
07/31/2007 23:15:54.266 machinetype = x86
07/31/2007 23:15:54.266 package = HotFixSqlxml4
07/31/2007 23:15:54.266 packagetype = Hotfix
07/31/2007 23:15:54.276 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
07/31/2007 23:15:54.276 productname = Redist9
07/31/2007 23:15:54.276 recommendinstall = 1
07/31/2007 23:15:54.276 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.276 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.286 splevel = 2
07/31/2007 23:15:54.286 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
07/31/2007 23:15:54.286 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.286 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
07/31/2007 23:15:54.286 version = 9
07/31/2007 23:15:54.286
07/31/2007 23:15:54.296 File Group Details: MSI
07/31/2007 23:15:54.296 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.296 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.296 File Details: sqlxml4.msi
07/31/2007 23:15:54.296
07/31/2007 23:15:54.296 Instance Details: SQLXML4
07/31/2007 23:15:54.306 fullversion = 9.00.2047.00
07/31/2007 23:15:54.306 lcid = 1033
07/31/2007 23:15:54.306 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
07/31/2007 23:15:54.306 qfelevel = 2047
07/31/2007 23:15:54.306 sp = -1
07/31/2007 23:15:54.316
07/31/2007 23:15:54.316 Product Enumeration Results:
07/31/2007 23:15:54.316 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSqlxml4_x64.inf
07/31/2007 23:15:54.316 baselinebuild = 1399
07/31/2007 23:15:54.316 build = 3042
07/31/2007 23:15:54.316 description = SQLXML4
07/31/2007 23:15:54.326 details = Service Pack for Microsoft SQLXML 4.0.
07/31/2007 23:15:54.326 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.326 kbarticle = KB921896
07/31/2007 23:15:54.326 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.326 lcid = 1033
07/31/2007 23:15:54.336 legalproductname = SQLXML4 (64-bit)
07/31/2007 23:15:54.336 machinetype = x64
07/31/2007 23:15:54.336 package = HotFixSqlxml4_x64
07/31/2007 23:15:54.336 packagetype = Hotfix
07/31/2007 23:15:54.336 productname = Redist9
07/31/2007 23:15:54.346 recommendinstall = 1
07/31/2007 23:15:54.346 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.346 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.346 splevel = 2
07/31/2007 23:15:54.346 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.356 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
07/31/2007 23:15:54.356 version = 9
07/31/2007 23:15:54.356
07/31/2007 23:15:54.356 File Group Details: MSI
07/31/2007 23:15:54.356 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.356 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.366 File Details: sqlxml4_x64.msi
07/31/2007 23:15:54.366
07/31/2007 23:15:54.366 Product Enumeration Results:
07/31/2007 23:15:54.366 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSQLServer2005_BC.inf
07/31/2007 23:15:54.366 baselinebuild = 1399
07/31/2007 23:15:54.376 build = 2004
07/31/2007 23:15:54.376 description = Backward Compatibility
07/31/2007 23:15:54.376 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
07/31/2007 23:15:54.376 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.376 kbarticle = KB921896
07/31/2007 23:15:54.386 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.386 lcid = 1033
07/31/2007 23:15:54.386 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
07/31/2007 23:15:54.386 machinetype = x86
07/31/2007 23:15:54.386 package = HotFixSQLServer2005_BC
07/31/2007 23:15:54.396 packagetype = Hotfix
07/31/2007 23:15:54.396 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
07/31/2007 23:15:54.396 productname = Redist9
07/31/2007 23:15:54.406 recommendinstall = 1
07/31/2007 23:15:54.406 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.406 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.406 splevel = 2
07/31/2007 23:15:54.406 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
07/31/2007 23:15:54.406 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.416 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
07/31/2007 23:15:54.416 version = 9
07/31/2007 23:15:54.416
07/31/2007 23:15:54.416 File Group Details: MSI
07/31/2007 23:15:54.416 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.416 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.426 File Details: SQLServer2005_BC.msi
07/31/2007 23:15:54.426
07/31/2007 23:15:54.426 Instance Details: Backward Compatibility
07/31/2007 23:15:54.426 fullversion = 8.05.1704
07/31/2007 23:15:54.436 lcid = 1033
07/31/2007 23:15:54.436 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
07/31/2007 23:15:54.436 qfelevel = 1704
07/31/2007 23:15:54.436 sp = -1
07/31/2007 23:15:54.436
07/31/2007 23:15:54.446 Product Enumeration Results:
07/31/2007 23:15:54.446 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSQLServer2005_BC_x64.inf
07/31/2007 23:15:54.446 baselinebuild = 1399
07/31/2007 23:15:54.446 build = 2004
07/31/2007 23:15:54.446 description = Backward Compatibility
07/31/2007 23:15:54.446 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
07/31/2007 23:15:54.457 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.457 kbarticle = KB921896
07/31/2007 23:15:54.457 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.457 lcid = 1033
07/31/2007 23:15:54.457 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
07/31/2007 23:15:54.467 machinetype = x64
07/31/2007 23:15:54.467 package = HotFixSQLServer2005_BC_x64
07/31/2007 23:15:54.467 packagetype = Hotfix
07/31/2007 23:15:54.467 productname = Redist9
07/31/2007 23:15:54.467 recommendinstall = 1
07/31/2007 23:15:54.467 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.477 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.477 splevel = 2
07/31/2007 23:15:54.477 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.477 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
07/31/2007 23:15:54.477 version = 9
07/31/2007 23:15:54.487
07/31/2007 23:15:54.487 File Group Details: MSI
07/31/2007 23:15:54.487 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.487 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.487 File Details: SQLServer2005_BC_x64.msi
07/31/2007 23:15:54.497
07/31/2007 23:15:54.497 Product Enumeration Results:
07/31/2007 23:15:54.497 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSqlWriter.inf
07/31/2007 23:15:54.497 baselinebuild = 1399
07/31/2007 23:15:54.497 build = 3042
07/31/2007 23:15:54.497 description = Microsoft SQL Server VSS Writer
07/31/2007 23:15:54.507 details = Service Pack for Microsoft SQL Server VSS Writer.
07/31/2007 23:15:54.507 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.507 kbarticle = KB921896
07/31/2007 23:15:54.507 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.517 lcid = 1033
07/31/2007 23:15:54.517 legalproductname = Microsoft SQL Server VSS Writer
07/31/2007 23:15:54.517 machinetype = x86
07/31/2007 23:15:54.517 package = HotFixSqlWriter
07/31/2007 23:15:54.517 packagetype = Hotfix
07/31/2007 23:15:54.527 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
07/31/2007 23:15:54.527 productname = Redist9
07/31/2007 23:15:54.527 recommendinstall = 1
07/31/2007 23:15:54.527 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.527 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.527 splevel = 2
07/31/2007 23:15:54.527 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
07/31/2007 23:15:54.537 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.537 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
07/31/2007 23:15:54.537 version = 9
07/31/2007 23:15:54.537
07/31/2007 23:15:54.537 File Group Details: MSI
07/31/2007 23:15:54.547 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.547 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.547 File Details: SqlWriter.msi
07/31/2007 23:15:54.547
07/31/2007 23:15:54.547 Instance Details: Microsoft SQL Server VSS Writer
07/31/2007 23:15:54.547 fullversion = 9.00.2047.00
07/31/2007 23:15:54.557 lcid = 1033
07/31/2007 23:15:54.557 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
07/31/2007 23:15:54.557 qfelevel = 2047
07/31/2007 23:15:54.557 sp = -1
07/31/2007 23:15:54.567
07/31/2007 23:15:54.567 Product Enumeration Results:
07/31/2007 23:15:54.567 INF File Name: c:\ace3346e16b7688715bb0ff855\HotFixSqlWriter_x64.inf
07/31/2007 23:15:54.567 baselinebuild = 1399
07/31/2007 23:15:54.567 build = 3042
07/31/2007 23:15:54.567 description = Microsoft SQL Server VSS Writer
07/31/2007 23:15:54.577 details = Service Pack for Microsoft SQL Server VSS Writer.
07/31/2007 23:15:54.577 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
07/31/2007 23:15:54.577 kbarticle = KB921896
07/31/2007 23:15:54.577 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
07/31/2007 23:15:54.577 lcid = 1033
07/31/2007 23:15:54.577 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
07/31/2007 23:15:54.587 machinetype = x64
07/31/2007 23:15:54.587 package = HotFixSqlWriter_x64
07/31/2007 23:15:54.587 packagetype = Hotfix
07/31/2007 23:15:54.587 productname = Redist9
07/31/2007 23:15:54.587 recommendinstall = 1
07/31/2007 23:15:54.587 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
07/31/2007 23:15:54.597 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
07/31/2007 23:15:54.597 splevel = 2
07/31/2007 23:15:54.597 supportdir = c:\ace3346e16b7688715bb0ff855
07/31/2007 23:15:54.597 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
07/31/2007 23:15:54.597 version = 9
07/31/2007 23:15:54.607
07/31/2007 23:15:54.607 File Group Details: MSI
07/31/2007 23:15:54.607 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
07/31/2007 23:15:54.607 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
07/31/2007 23:15:54.607 File Details: SqlWriter_x64.msi
07/31/2007 23:15:54.607
07/31/2007 23:16:19.753 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
07/31/2007 23:16:19.783 Registry: Cannot read registry key value "PendingFileRenameOperations"
07/31/2007 23:16:19.813 Registry: Read registry key value "EnableErrorReporting", DWORD value = 1
07/31/2007 23:16:19.813 Registry: Read registry key value "CustomerFeedBack", DWORD value = 1
07/31/2007 23:16:20.714 Registry: Set registry key value "EnableErrorReporting", DWORD value = 1
07/31/2007 23:16:20.714 Registry: Set registry key value "CustomerFeedBack", DWORD value = 1
07/31/2007 23:16:20.774 Locked file: Checking for locked files
07/31/2007 23:16:45.530 Attempting to pause the 32 bit ngen queue
07/31/2007 23:16:46.371 Installing product: SQLTools9
07/31/2007 23:16:46.381 Installing instance: SQL Tools
07/31/2007 23:16:46.411 Installing target: MSTS0000
07/31/2007 23:16:46.411 Installing file: sqlrun_tools.msp
07/31/2007 23:16:46.451 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
07/31/2007 23:16:46.451 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/31/2007 23:16:46.451 Registry: Cannot read registry key value "Debug"

Somebody help me in this issue..Please....

|||

did you check this,

Registry: Cannot read registry key value "PendingFileRenameOperations"
Registry: Cannot read registry key value "Debug"

dunno if this is the reason....

MS SQL Server 2005 SP2 Problems with SSIS packages

I installed SP2 to one of our servers to see what we'd need to do for our Production systems. The server in question is used for a log shipped copy of production, SSRS, SSIS and general duty stuff. I got errors in two areas during the installation -- 1 dealing with SSNS (don't use it yet on that server) and the second being the Client product.

After a reboot I went into a Business Studio solution I've been working on (and using) for several months. None of my packages are working--each having the following problem:

Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90'.
This operation failed because the QueryInterface call on the COM component for the interface with IID '{8BDFE892-E9D8-4D23-9739-DA807BCDC2AC}'
failed due to the following error: Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED))..

It seems to be in the designer as it is unable to display the the graphical version but it does let me switch to the code view.

What is the easiest way to troubleshoot and/or fix this?

For some reason it didn't register the new DTS.DLL correctly. Running

regsvr32 “C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"

made the problem go away. Things that make you go 'hmmmmmmmmm'.

I wonder what else is busted...

MS SQL 2005 SP2 x64 & SSIS Packages

On my local desktop, I can create and run ssis packages, when I try to do the same thing on server I get he following error right clicking on running packages or stored packages.

failed to retrieve data for this request. Library not Registered. (exception from HRESULT: 0x8002801D

there are 2 instances of SQL on this server. Both are named with one being use by SQLExpress and the other by SQL2005 Std

Give this a try; Integration Services installs just once no matter how many instances are installed on the machine. For the instance you are wishing to work with you can change the instance viewed by modifying C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml

Change the entry below to match your instance name.

--Prior to change

<ServerName>.</ServerName>

--After change

<ServerName>MySQLServer\MySQLInstancename</ServerName>

|||

Hi,

This is setup problem, partially discussed in this KB: http://support.microsoft.com/kb/919224

If reapplying SP2 to both instances does not work, please run the following command to manually fix it (the KB is to be modified soon):

%windir%\syswow64\regsvr32 "%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll”

|||Still no luck|||

I'm still getting same error. I do not have the hotfix installed do I need it?

Microsost SQL Server Management Studio

Failed to retrieve data for this request. ( Microsoft.SqlServer.SmoEnum)

Additional Information:

Library not registered.( Exception from HRESULT: 0x80002801D(TYPE_E_LIBNOTREGISTERED))

(Microsoft.SqlServer.DTSRuntimeWrap)

Library not registered.( Exception from HRESULT: 0x80002801D(TYPE_E_LIBNOTREGISTERED))

(Microsoft.SqlServer.DTSRuntimeWrap)

MS SQL 2005 SP2 x64 & SSIS Packages

On my local desktop, I can create and run ssis packages, when I try to do the same thing on server I get he following error right clicking on running packages or stored packages.

failed to retrieve data for this request. Library not Registered. (exception from HRESULT: 0x8002801D

there are 2 instances of SQL on this server. Both are named with one being use by SQLExpress and the other by SQL2005 Std

Give this a try; Integration Services installs just once no matter how many instances are installed on the machine. For the instance you are wishing to work with you can change the instance viewed by modifying C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml

Change the entry below to match your instance name.

--Prior to change

<ServerName>.</ServerName>

--After change

<ServerName>MySQLServer\MySQLInstancename</ServerName>

|||

Hi,

This is setup problem, partially discussed in this KB: http://support.microsoft.com/kb/919224

If reapplying SP2 to both instances does not work, please run the following command to manually fix it (the KB is to be modified soon):

%windir%\syswow64\regsvr32 "%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll”

|||Still no luck|||

I'm still getting same error. I do not have the hotfix installed do I need it?

Microsost SQL Server Management Studio

Failed to retrieve data for this request. ( Microsoft.SqlServer.SmoEnum)

Additional Information:

Library not registered.( Exception from HRESULT: 0x80002801D(TYPE_E_LIBNOTREGISTERED))

(Microsoft.SqlServer.DTSRuntimeWrap)

Library not registered.( Exception from HRESULT: 0x80002801D(TYPE_E_LIBNOTREGISTERED))

(Microsoft.SqlServer.DTSRuntimeWrap)

ms sql 2005 developer edition

is it possible to install ms sql 2005 developer edition databse server
on window XP professional version 2002 with SP2 or just allows install
client version?On Oct 3, 10:39 am, HandersonVA <handerso...@.hotmail.comwrote:

Quote:

Originally Posted by

is it possible to install ms sql 2005 developer edition databse server
on window XP professional version 2002 with SP2 or just allows install
client version?

Of course you can - the only version you can't install on a client
machine is the SQL Server Enterprise Edition!

JC
xSQL Software
http://www.xsqlsoftware.com|||On Oct 3, 12:23 pm, xman <x...@.xsqlsoftware.comwrote:

Quote:

Originally Posted by

On Oct 3, 10:39 am, HandersonVA <handerso...@.hotmail.comwrote:
>

Quote:

Originally Posted by

is it possible to install ms sql 2005 developer edition databse server
on window XP professional version 2002 with SP2 or just allows install
client version?

>
Of course you can - the only version you can't install on a client
machine is the SQL Server Enterprise Edition!
>
JC
xSQL Softwarehttp://www.xsqlsoftware.com

thank you for your comments!
I just tried to install ms sql 2005 developer edition on my home
computer which has win XP professional, but it says I can only install
the client version to connect the database server. It does not allow
me to install whole database server.|||HandersonVA (handersonva@.hotmail.com) writes:

Quote:

Originally Posted by

I just tried to install ms sql 2005 developer edition on my home
computer which has win XP professional, but it says I can only install
the client version to connect the database server. It does not allow
me to install whole database server.

Then I would guess you need to look twice on the CD/DVD. It sounds as
if you have a copy of Enterprise Edition.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

MS SQL 2005 + Windows Server 2003 SP2

At first I thought it was just me, but has anyone else noticed that SQL 2005 suffers a performance hit when you install Windows Server 2003 SP2?

Since SP2, memory and hard drive usage has gone through the roof on a number of servers I use. It may just be coincidence... but it seems unlikely.

We are running one of our production clusters on Windows Server 2003 x64 SP2 and SQL Server 2005 x64 SP2 (Build 3159) without any trouble.

We also recently upgrade our development servers to Win2K3 x64 SP2 and SQL Server 2005 x64 SP2 (Build 3175) again without any issues so far.

Which build of SQL Server are you running?

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||I think really just coincidence. Can you reccomend is the first step to diagnosing a SQL 2005 server's performance issues?|||

Here are a couple of blog posts that might help:

http://glennberrysqlperformance.spaces.live.com/blog/cns!45041418ECCAA960!526.entry

http://glennberrysqlperformance.spaces.live.com/blog/cns!45041418ECCAA960!356.entry

|||Nice posts, thanks Glenn.

MS SQL 2000 after patching with SP3

I have patched my MS SQL 2000 DB from SP2 to SP3.

I noticed from the enterprise manager the patch level indicates
8.00.760 (SP3).

However, using microsofts type 4 JDBC driver to connect to SQL2000, I got the following info when I used one of the APIs to retrieve the database version :

Microsoft SQL Server 2000 - 8.00.534 (Intel X86) Nov 19 2001 13:23:50 Copyright (c) 1988-2000 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3) .

Now... which one is having the bug? MS JDBC driver or MS SQL 2000 SP3 ??8.00.760 = 2000 SP3. JDBC was written before SP3.
Look at %windir%\sqlsp.log to see SP3 is correctly installed.|||Originally posted by ispaleny
8.00.760 = 2000 SP3. JDBC was written before SP3.
Look at %windir%\sqlsp.log to see SP3 is correctly installed.

Indeed Type 4 MS JDBC driver is written b4 service pack 3.

However, after patching MS SQL 2000, the driver should correctly retrieve the info from SQL 2000. Don't suppose that the JDBC driver has that value hard-coded in its coding?

Probably I would temporary revert to the JDBC-ODBC bridge to do a simple check..|||I tried to patch SP3 on MS sql 2000 standard edition, the JDBC driver reports it correctly.

Thus, seems like the only problem occurs on my MS Sql2000 Enterprise Edition.

MS search

Hello,
I have a SQL 7 sp2 server without MS search service installed. The server
has been running for a few years. Can I install the Search service now? How
would I do this?
Thanks
jjYou should be able to insert the installation CD, run setup and add that
component.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"jj" <jeff_detoro@.urmc.rochester.edu> wrote in message
news:OUQJzBiqDHA.2528@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I have a SQL 7 sp2 server without MS search service installed. The server
> has been running for a few years. Can I install the Search service now?
How
> would I do this?
>
> Thanks
> jj
>