Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

we have a dev server. First we had SQL 2000 (default instance), when SQL 2005 came out, we installed it as a named instance. Nowadays we barely use the SQL2000 instance, but this is the default. We would like the SQL2005 to be the default instance and make the 2000 a named one. Is this even possible?

Thank you!

share|improve this question

2 Answers 2

up vote 5 down vote accepted

Unfortunately, no. You'll need to upgrade the default instance to SQL 2005, remove the 2005 named instance and reinstall SQL 2000 as a named instance. Or just wipe clean and install SQL 2005 first as the default and SQL 2000 as a named instance.

Any reason you need to keep the SQL 2000 instance around?

share|improve this answer
    
Mmm no... I think we could live without SQL2000, later if we need it, then we can install it as a named instance... So... I need to uninstall both sql 2000 and 2005 and install 2005 as a default instance. How can I backup the databases, logins, agent schedules etc??? –  emzero Jan 5 '10 at 21:34
    
No need to uninstall. Although it is a touch cleaner it is a pain. You can upgrade your SQL 2000 instance to 2005. Just run the SQL 2005 installer and choose to upgrade the default instance. –  squillman Jan 5 '10 at 22:01
    
I decided to uninstall the SQL2000. So now I have one named instance of sql2005... if I run the setup I should be able to install a sql2005 as the default instance right? But then I need to move everything from the named instance to the fresh new default instance. Any idea how to do that quick and easy? –  emzero Jan 5 '10 at 22:13
    
Yes, install 2005 as the default instance. Note, however, that patching is instance specific so you'll need to bring it up to the same patch level as your named instance. You can detach/attach databases (or use the copy db wizard which will bring over other objects as well) to move things. –  squillman Jan 5 '10 at 22:18

I did step 1 and 2 from here and it worked. Didn't have to reinstall SQL Server.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.