Change Named to Default Instance

We are looking to install SQL 2005 Standard next to a SQL 2000 Enterprise
installation. The SQL 2K install is running under the default instance and
therefore to install the SQL 2005 we will need to run it under a named
instance. After the SQL 2005 has been configured and we are confident the DB
is how we want it we want to uninstall the SQL 2K and make the SQL 2005 the
default instance. Can anyone describe the steps need to do this. We want to
avoid having to re-write a lot of connetion strings in client applications
which would require is to re-deploy those apps.
Thanks in advance.
RTYou cannot change instance name, nor from a default to a named instance (or
other way around). One
option is to install 2005 again, as a named instance (after removing 2000).
Then copy the databases
(backup/restore, detach/attach, for instance). But there are extra steps han
dling the data inside
the system databases, though...
Or, handle this on the client machines:
Either change the connection string.
Or, create an alias for the named instance, with only the machine name as th
e alias name.
(Basically, rename it seen from the client's perspective.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RT" <RT@.discussions.microsoft.com> wrote in message
news:2BD744AB-1A64-4F49-8FE5-9A388A52B72D@.microsoft.com...
> We are looking to install SQL 2005 Standard next to a SQL 2000 Enterprise
> installation. The SQL 2K install is running under the default instance and
> therefore to install the SQL 2005 we will need to run it under a named
> instance. After the SQL 2005 has been configured and we are confident the
DB
> is how we want it we want to uninstall the SQL 2K and make the SQL 2005 th
e
> default instance. Can anyone describe the steps need to do this. We want t
o
> avoid having to re-write a lot of connetion strings in client applications
> which would require is to re-deploy those apps.
> Thanks in advance.
> RT|||Hi,
To add on to Tibor; you could use the automated upgrade of sql 2000 to sql
2005. steps
1. Take a complete backup of sql 2000 (including system databases)
2. Run the SQL 2005 setup program
3. This will automatically upgrades the existing SQL 2000 to SQL 2005
4. After the completion of the upgrade the existing SQL 2000 will be
upgraded to SQL 2005 with the same server name
5. After this there will not be any connecting string chnages
The only this incase of issues; you may need to install SQL 2000 and restore
all the databases backed up...
Take a look into:-
http://www.microsoft.com/technet/pr...5/sqlupgrd.mspx
Thanks
Hari
"RT" <RT@.discussions.microsoft.com> wrote in message
news:2BD744AB-1A64-4F49-8FE5-9A388A52B72D@.microsoft.com...
> We are looking to install SQL 2005 Standard next to a SQL 2000 Enterprise
> installation. The SQL 2K install is running under the default instance and
> therefore to install the SQL 2005 we will need to run it under a named
> instance. After the SQL 2005 has been configured and we are confident the
> DB
> is how we want it we want to uninstall the SQL 2K and make the SQL 2005
> the
> default instance. Can anyone describe the steps need to do this. We want
> to
> avoid having to re-write a lot of connetion strings in client applications
> which would require is to re-deploy those apps.
> Thanks in advance.
> RT