Running 2000 and 2005 Sql Server on 1 machine

I'm currently running SQL Server 2000 and 2005 on one machine at least I
think I am. I have Enterprise Manager and all the other components for 2000
on my laptop. I also loaded SQL Server 2005 with the .NET application from a
CD that I got from a Microsoft convention a long time ago. Basically, my
problem is when I click on the SQL SERVER 2005 Management Studio and run a
SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
database in 2005 and the mdf and ldf files are stored in the C:\...\Microsof
t
SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
am I doing wrong? Can 2000 and 2005 not run on the same box? This is
preventing me from changing the database compatiblity level to 90 because it
doesn't show up. Can anyone help? or suggest what I should do?
-- TCI guess you are connecting to your SQL Server 2000 Instance using SQL Server
Management Studio. That's why it tells you it's 2000 when you run SELECT
@.@.VERSION.
Go to SQL Server Configuration Manager and see if your SQL Server 2005
instance is running. And connect to that instance using SSMS. So, you'll be
able to create databases compatibility level 90.
Ekrem ?nsoy
"Terrance" <Terrance@.discussions.microsoft.com> wrote in message
news:8EC78FDB-283B-4391-A9D9-6BEB46BC7F9C@.microsoft.com...
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for
> 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
> a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the
> C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory.
> What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
> it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC|||Hi Terrance
Along with the other posts!! The second instance (i.e. SQL 2005) would be
installed as a named instance, therefore you should know what instance has
been connected to.
I would not expect the SQL Server 2000 instance to know if the
...\MSSQL.1\BIN directory as the MSSQL.1 directory naming was introduced in
SQL 2005. Even for the SQL 2005 instance you would expect the database files
to be put into ...\MSSQL.1\MSSQL\DATA How are you creating this database?
For a
SQL 2005 instance you can right click the instance in SSMS and choose
properties then the Database Settings will tell you the default data and log
directories, a CREATE DATABASE in a query window without specifying any of
the file names will use these directories.
To see or set the databases compatability level use sp_dbcmptlevel
EXEC sp_dbcmptlevel AdventureWorks;
GO
EXEC sp_dbcmptlevel AdventureWorks, 90;
GO
It is best to change compatibility while no users are connected to the
database!
John
"Terrance" wrote:

> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for 200
0
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the C:\...\Micros
oft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. Wha
t
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TCsql