SQL SERVER2005-DeveloperEdition

Russel is right, but be aware that this is a ONE WAY conversion--you can't
change it back. Changing the compatibility level will also trigger a series
of operations that will find the version 8 (SQL Server 2000) to version 9
(SQL Server 2005) issues and incompatibilites. These must be corrected
before the conversion will be permitted to complete.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Russell Fields" wrote in message

> Alina Florence,
>
> I would assume that your mean your database is showing version 8.0, not
> the server itself. If that is correct,the run the following command:
>
> sp_dbcmptlevel @dbname = 'Your80Database', @new_cmptlevel = 90
>
> You can also set this property from Management Studio by editing the
> database properties, go to the options panel, and set the compatibility
> level there.
>
> RLF
>
> "AlinaFlorence" wrote in message
>
>>I have installed SQL2005 Dev.Edition. But its showing the version 8.0 and
>>it
>> is not the version 9.0. The problem is only SQL SERVER2000 queries are
>> working and not SQL2005.
>> May anyone help me out?
>
>
 >> Stay informed about: SQL SERVER2005-DeveloperEdition 

When a SQL Server 2000 database is restored or attached to a SQL Server 2005
server, the database is converted to 2005 format. So that part is not
reversible and the database cannot then be restored to a SQL Server 2000
server. The database compatibility level (80, 90) only controls how T-SQL
executes and some other rules are applied.

Therefore, the database can be switched back and forth between 80 and 90.
But there are some commands/syntax that only work in one of these versions,
so T-SQL will only work according to the compatibility level of the
database. (I have rolled some forward to 90 that I had to later roll back
because the (commercial) application was not fully ready for 90 mode.)

RLF

"William Vaughn" wrote in message

> Russel is right, but be aware that this is a ONE WAY conversion--you can't
> change it back. Changing the compatibility level will also trigger a
> series of operations that will find the version 8 (SQL Server 2000) to
> version 9 (SQL Server 2005) issues and incompatibilites. These must be
> corrected before the conversion will be permitted to complete.
>
> --
> __________________________________________________________________________
> William R. Vaughn
> President and Founder Beta V Corporation
> Author, Mentor, Dad, Grandpa
> Microsoft MVP
> (425) 556-9205 (Pacific time)
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> ____________________________________________________________________________________________
> "Russell Fields" wrote in message
>
>> Alina Florence,
>>
>> I would assume that your mean your database is showing version 8.0, not
>> the server itself. If that is correct,the run the following command:
>>
>> sp_dbcmptlevel @dbname = 'Your80Database', @new_cmptlevel = 90
>>
>> You can also set this property from Management Studio by editing the
>> database properties, go to the options panel, and set the compatibility
>> level there.
>>
>> RLF
>>
>> "AlinaFlorence" wrote in
>> message
>>>I have installed SQL2005 Dev.Edition. But its showing the version 8.0 and
>>>it
>>> is not the version 9.0. The problem is only SQL SERVER2000 queries are
>>> working and not SQL2005.
>>> May anyone help me out?
>>
>>
>
 >> Stay informed about: SQL SERVER2005-DeveloperEdition