January 18, 2009 at 1:06 am
Please:
(1) We tried to do an upgrade from SQL Server 2000 to SQL Server 2005 on a Windows 2003 Small Business Server.
(2) There were 3 instances of SQL Server on the machine before we started the upgrade. We don't know why (maybe because some came pre-installed with the Small Business Server?). Only one instance had a user database -- our production database.
(3) We stopped all SQL Server services, stared the upgrade program, and specifically selected the named instance (associated with out production database) to be upgraded.
(4) The installation ran without reporting an error.
(5) But when we connected to the named instance through Management Studio . . . the version of the server remained 8.0.2039 -- SQL Server 2000. And our production database is still attached to it.
(6) It's as if no SQL Server 2005 had been installed at all -- but only Management Studio.
(7) What did we not understand about this?
Thanks.
January 18, 2009 at 4:27 am
SBS installs 2 desktop engine instances. One for Sharepoint and one for SBSMonitoring.
Can you post a registry screenshot of the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 18, 2009 at 9:06 am
As Perry mentioned, you can have multiple instances and an upgrade will target one. Someone would have targeted one and the others would remain untouched. That's the idea of instances, they work separately.
January 18, 2009 at 10:09 am
Right -- what does this tell us please?
January 18, 2009 at 10:12 am
No values there?
What SQL Server services do you see? (In the Control Panel/Admin tools/Services
January 18, 2009 at 10:23 am
so besides the 2 default desktop engines you have an instance
MSSQL$COW0, what instance are you logging into via SSMS?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 18, 2009 at 10:25 am
Apparently . . . four instances of MSSQLSERVER and 4 corresponding SQLAgents.
But they're all SS2000, as best I can figure . . .
January 18, 2009 at 10:27 am
I'm accessing COW0 with Management Studio -- that's got our production database and it's okay. It's just coming up as 2000.
January 18, 2009 at 10:28 am
yes just seen the COW0 instance in the registry too. Scroll across to the right on the right hand pane, what are the installed instances?
what instance name are you typing into the SSMS connection dialog box
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 18, 2009 at 10:31 am
Four installed instances. I'm connecting to COW0 -- which comes up fine as far as it goes, but it's 8.0 . . .
January 18, 2009 at 10:31 am
it seems you have 2 instances referencing COW0, my guess is you upgraded the wrong one hence why you see the sql2000 version number. Are the 2 extra instances MSDE or full blown SQL2000
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 18, 2009 at 10:31 am
You've got SQL 2005 installed, the image shows that.
I'd connect with SSMS to each instance separately (browse for them) and then run select @@version. That will show you what you have.
Then you can upgrade those that you need to. Don't click "next" on the upgrade without reading each screen. There's one where you select the instance. And be sure you have good backups.
January 18, 2009 at 10:32 am
installed instances:
SBSMONITORING
MSSQLSERVER
COW0
MSSQL$COW0
January 18, 2009 at 10:36 am
Okay -- thanks.
Let me see what happens when I try to connect to each of the instances . . .
January 18, 2009 at 10:45 am
as well as the version get the following
select @@servername, serverproperty('servername')
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 15 posts - 1 through 15 (of 30 total)
You must be logged in to reply to this topic. Login to reply