| Author |
Topic |
|
Dextar
Starting Member
6 Posts |
 Posted - 2009-09-08 : 00:04:00
|
| i have a sql server 2000( default named version) Enterprise edition SP4 on windows server 2003 and i have installed sql server 2005 ( default named version) with all features( SSIS, Analysis service , report server ) but after instalation and logging in sql server management studio i am not able to see compatibility level 90 if create new database , it shows version 8.xx in front of local database name.i dont have 2000 dump but can reinstal 2005 can i make it named and can use sql server 2005 with full featuresThanks and Regards |
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2009-09-08 : 00:14:56
|
I think you need to change the existing database compatibility level to 90 manually. I don't think installation will do that for you.When you create a new database, SQL Server will copy it over from model DB. Change model DB to 90 first and create the new database.
KH[spoiler]Time is always against us[/spoiler] |
 |
|
|
Dextar
Starting Member
6 Posts |
Posted - 2009-09-08 : 00:17:52
|
| But it is not showing compatibilty level 90 in compatibility list |
|
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2009-09-08 : 01:17:01
|
did you do a upgrade from 2000 or install the 2005 as a new instance ?see http://msdn.microsoft.com/en-us/library/ms144245%28SQL.90%29.aspx on upgrade your SQL 2000 to 2005
KH[spoiler]Time is always against us[/spoiler] |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-09-08 : 03:26:08
|
quote:
Originally posted by Dextar
But it is not showing compatibilty level 90 in compatibility list
Run SELECT @@Version please--Gail ShawSQL Server MVP |
|
|
|
Dextar
Starting Member
6 Posts |
Posted - 2009-09-08 : 03:50:08
|
| Microsoft SQL Server 2000 - 8.00.2039 when i run the command in management studio with local server |
|
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2009-09-08 : 05:03:36
|
quote:
Originally posted by Dextar
Microsoft SQL Server 2000 - 8.00.2039 when i run the command in management studio with local server
that means the SSMS is connected to a SQL 2000 Server.
KH[spoiler]Time is always against us[/spoiler] |
|
|
|
Dextar
Starting Member
6 Posts |
Posted - 2009-09-08 : 05:19:11
|
| sql server 2005 is installed with default name instance , then how should i connect to sql server 2005 |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-09-08 : 05:32:28
|
| Both 2000 and 2005 cannot be the default instance. One of them (or both) has to be a named instance. Go to the SQL 2005 folder in the start menu, expand Configuration tools and open the SQL configuration manager. Take a look at the SQL 2005 services, it'll show the name, if it's a named instance.--Gail ShawSQL Server MVP |
|
|
|
Dextar
Starting Member
6 Posts |
Posted - 2009-09-08 : 05:50:45
|
| Thanks a lot , i have checked the configuration manager in that three option are showing 1) sql server 2005 services a) SS Integration S b) SSAS c) SS Reproting S d) SS Browser2) SQL Server 2005 network configuration 3) SQL Native CLient under aliases i dont find any thing Kindly guide if i can repair 2005 to create a named instance or any way forward |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-09-08 : 10:53:58
|
| Then it looks like the DB engine did not install at all. Try running install again and check that you do select the DB engine (and that there's no failure during the installation)--Gail ShawSQL Server MVP |
|
|
|
Dextar
Starting Member
6 Posts |
Posted - 2009-09-09 : 00:29:04
|
| Gail , yup you were right the database engine was not there i again installed the engine part from setup as named instance and it worked ...thanks a lot for the help |
|
|
|
|
SQL server 2005 not showing compatiblity mode 90