New SQL 2005 instance using 2000 engine?

Hello,
I installed SQL 2005 Standard on the same server (2K3) with SQL 2000. My named instance I installed is coming up with "Version 8.00.2039" in the Server Management Studio and will not let me restore a database back-up I made on a 2005 development workstation (I'm assuming it's because it's trying to use the 2000 engine instead of the 2005). Is there a way I can force this instance to use the 2005 engine rather than the 2000?

Thanks,

Steve

SQL 2005 will not use the 2000 engine.

It sounds like your connecting to the wrong instance, try running

select @.@.VERSION

you should see something like :

Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

for 2005.

To double check you connection string, e.g. your instance name. Try the following :

Run SQL Server 2005 Surface Area Configuration
Click "Surface Area Configuration for Services and Connections

You will see your SQL2005 Instances, expand the SQL instance, expand Database Engine, click Service.

Note the Display Name "In my instance its SQL Server (SQLEXPRESS)"

Run services.msc

Select the SQL server name from the display named noted above.

Select properties

Copy the Path to execute, in my instances its :

"c:\Program Files (x86)\Microsoft SQL Server\MSSQL.4\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS

Run this from a cmd line.

Look at the output, you looking for :

Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].

For me, I can connect on \\SERVERNAME\SQLExpress

for my SQL instance, eg not SQL Express I get :

Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]

So, we have NO instance (MSSQLSERVER is the default), so to connect we just connect to \\SERVERNAME

Let me know if this helps.

Thanks

Steve

|||Yup, that was exactly what happened. I apparently created a 2000 instance instead of a 2005 instance in my late night stupor, and was convinced it was suppose to be 2005. =)

Thanks!|||

Yep, I have seen that done before, I have even seen someone rebuild a SQL server from stracth as they were convinced that somehow the instance was 'broke'

glad to be of help.

Steve