-
SQL2K upgrade to 2005
I upgraded a SQL2K EE to 2005 EE. If I go to About it shows the version as 9.00.2047.00 but when I use a query 'select @@version', its showing SQL Server 2000 - 8.00.2039
-
SSMS is 9.00.2047
MDAC 2000.086
Analysis Services 9.00.2047
Integration Services 9.00.2047
Reporting Services 9.00.2047
Looks like the Database Services didn't upgrade. I've already installed SP1
-
What's sql service name now? What's version number in sql server log?
-
In place upgrade is a pain, I had many problems with one server. Did you check the installation log files?.
One of the problems I had was using software from networked mapped drive (copying to local and running is best but you can use UNC path too).
-
SQL Server is still showing MSSQLSERVER not SQL Server.
I've reverted back to the snapshot before we tried the upgrade. The problem is after choosing the Instance and the Existing Components doesn't give me the opportunity to mark any component.
-
Here's the log file today:
2007-10-01 13:31:13.59 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-10-01 13:31:13.60 server Copyright (C) 1988-2002 Microsoft Corporation.
2007-10-01 13:31:13.60 server All rights reserved.
2007-10-01 13:31:13.60 server Server Process ID is 1532.
2007-10-01 13:31:13.60 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-10-01 13:31:13.67 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2007-10-01 13:31:13.74 server SQL Server configured for thread mode processing.
2007-10-01 13:31:13.76 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2007-10-01 13:31:13.82 server Attempting to initialize Distributed Transaction Coordinator.
2007-10-01 13:31:15.12 spid2 Starting up database 'master'.
2007-10-01 13:31:16.99 spid2 0 transactions rolled back in database 'master' (1).
2007-10-01 13:31:16.99 spid2 Recovery is checkpointing database 'master' (1)
2007-10-01 13:31:17.20 spid5 Starting up database 'model'.
2007-10-01 13:31:17.20 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-10-01 13:31:17.23 server SQL server listening on 10.1.150.40: 1433.
2007-10-01 13:31:17.23 server SQL server listening on 10.1.1.80: 1433.
2007-10-01 13:31:17.23 server SQL server listening on 127.0.0.1: 1433.
2007-10-01 13:31:17.24 spid2 Server name is 'NYCGPTEST02'.
2007-10-01 13:31:17.24 spid8 Starting up database 'msdb'.
2007-10-01 13:31:17.26 spid9 Starting up database 'pubs'.
2007-10-01 13:31:17.26 spid10 Starting up database 'Northwind'.
2007-10-01 13:31:17.26 server SQL server listening on TCP, Shared Memory, Named Pipes.
2007-10-01 13:31:17.28 server SQL Server is ready for client connections
2007-10-01 13:31:17.28 spid11 Starting up database 'DYNAMICS'.
2007-10-01 13:31:17.28 spid12 Starting up database 'ILXUS'.
2007-10-01 13:31:17.32 spid13 Starting up database 'ILXPH'.
2007-10-01 13:31:17.32 spid14 Starting up database 'ILXUK'.
2007-10-01 13:31:17.32 spid15 Starting up database 'TEST'.
2007-10-01 13:31:17.59 spid9 Starting up database 'ReportServer'.
2007-10-01 13:31:17.65 spid10 Starting up database 'ReportServerTempDB'.
2007-10-01 13:31:17.68 spid5 Clearing tempdb database.
2007-10-01 13:31:17.81 spid5 Starting up database 'tempdb'.
2007-10-01 13:31:17.89 spid8 Starting up database 'Staging'.
2007-10-01 13:31:22.71 spid2 Recovery complete.
2007-10-01 13:31:22.73 spid2 SQL global counter collection task is created.
2007-10-01 13:31:22.84 spid2 Launched startup procedure 'smDEX_Build_Locks'
2007-10-01 13:34:44.29 spid51 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'sp_MSgetversion'.
2007-10-01 14:51:38.50 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
-
Looks like you only get sql2k5 client tools installed, didn't perform upgrade. Version number in ssms -> about is tool's version number, not sql engine's.
-
can i just install a new named instance then detach/attach sql 2000 database since the default instance won't upgrade?
-
Yes you can, but I rather do backup/restore. You can go back to sql2k easily if anything wrong in sql2k5.
-
everything is looking good after creating the new instance and testing. the plan is to turn off the SQL2K services for now but is it easy enough to uninstall sql2k(maybe after 3-4 months)
-
Uninstall is always easier than install.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|