Renaming a named instance of SQL Server 2005

I installed a named instance of SQL Server 2005 on a machine...let's
say I called it VAIO4. I want to rename it to BTSERVER. I'd rather not
have to uninstall and reinstall, but will do that if I have to. Is
there a way to rename the named instance without uninstall/reinstall?Unfortunately, you'll have to do the de-install/reinstall thing.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
<broy@.omegasoftwareinc.com> wrote in message
news:1150329868.510319.124590@.p79g2000cwp.googlegroups.com...
I installed a named instance of SQL Server 2005 on a machine...let's
say I called it VAIO4. I want to rename it to BTSERVER. I'd rather not
have to uninstall and reinstall, but will do that if I have to. Is
there a way to rename the named instance without uninstall/reinstall?|||Thanks Tom...
Just FMI, wasn't this something that could be done in SQL Server 2000
without uninstall/reinstall? Did the capability disappear with SQL
Server 2005 or was it never there even in 2000?|||I don't recall it being a possibility with 2000. However, it's been on my
wish list for a good long time. Don't get me started... ;-)
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
<broy@.omegasoftwareinc.com> wrote in message
news:1150334059.199056.4380@.h76g2000cwa.googlegroups.com...
Thanks Tom...
Just FMI, wasn't this something that could be done in SQL Server 2000
without uninstall/reinstall? Did the capability disappear with SQL
Server 2005 or was it never there even in 2000?|||OK, OK, won't get you started (or did I already?!). Just another quick
question for you, though. What if want another named instance of SQL
Server 2005 on the machine. Do I need to go through another install to
do that or is there another way to "spawn" another named instance on
the machine without getting rid of the current one?|||Nope, you gotta do one install per instance. Kinda makes sense, since each
instance could be a different version or different Service Pack level.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
<broy@.omegasoftwareinc.com> wrote in message
news:1150336619.432501.214330@.h76g2000cwa.googlegroups.com...
OK, OK, won't get you started (or did I already?!). Just another quick
question for you, though. What if want another named instance of SQL
Server 2005 on the machine. Do I need to go through another install to
do that or is there another way to "spawn" another named instance on
the machine without getting rid of the current one?|||it's actually possible. (WARNING: do at your own perils!)
1. drop current instname (sp_dropserver)
2. add new instance name (sp_addserver 'new name','local')
3. stop sqlserver
4. modify hklm\software\microsoft\microsoft sql server\
5. modify hklm\system\mssql$<instance>
6. use "sc create" to add new mssql$<inst>
7. start up with new inst_name - voila!
-oj
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23eYqXqBkGHA.2200@.TK2MSFTNGP05.phx.gbl...
>I don't recall it being a possibility with 2000. However, it's been on my
> wish list for a good long time. Don't get me started... ;-)
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> <broy@.omegasoftwareinc.com> wrote in message
> news:1150334059.199056.4380@.h76g2000cwa.googlegroups.com...
> Thanks Tom...
> Just FMI, wasn't this something that could be done in SQL Server 2000
> without uninstall/reinstall? Did the capability disappear with SQL
> Server 2005 or was it never there even in 2000?
>|||oops. #5 should be "modify
hklm\system\currentcontrolset\services\mssql$inst"
--
-oj
"oj" <nospam_ojngo@.home.com> wrote in message
news:elptQuCkGHA.1276@.TK2MSFTNGP03.phx.gbl...
> it's actually possible. (WARNING: do at your own perils!)
> 1. drop current instname (sp_dropserver)
> 2. add new instance name (sp_addserver 'new name','local')
> 3. stop sqlserver
> 4. modify hklm\software\microsoft\microsoft sql server\
> 5. modify hklm\system\mssql$<instance>
> 6. use "sc create" to add new mssql$<inst>
> 7. start up with new inst_name - voila!
>
> --
> -oj
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23eYqXqBkGHA.2200@.TK2MSFTNGP05.phx.gbl...
>>I don't recall it being a possibility with 2000. However, it's been on my
>> wish list for a good long time. Don't get me started... ;-)
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Toronto, ON Canada
>> .
>> <broy@.omegasoftwareinc.com> wrote in message
>> news:1150334059.199056.4380@.h76g2000cwa.googlegroups.com...
>> Thanks Tom...
>> Just FMI, wasn't this something that could be done in SQL Server 2000
>> without uninstall/reinstall? Did the capability disappear with SQL
>> Server 2005 or was it never there even in 2000?
>|||The problem is that 'do at your own perils!' How does one know that all the
references to the old instance name have been changed everywhere?
Linchi
"oj" wrote:
> it's actually possible. (WARNING: do at your own perils!)
> 1. drop current instname (sp_dropserver)
> 2. add new instance name (sp_addserver 'new name','local')
> 3. stop sqlserver
> 4. modify hklm\software\microsoft\microsoft sql server\
> 5. modify hklm\system\mssql$<instance>
> 6. use "sc create" to add new mssql$<inst>
> 7. start up with new inst_name - voila!
>
> --
> -oj
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23eYqXqBkGHA.2200@.TK2MSFTNGP05.phx.gbl...
> >I don't recall it being a possibility with 2000. However, it's been on my
> > wish list for a good long time. Don't get me started... ;-)
> >
> > --
> > Tom
> >
> > ----
> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> > SQL Server MVP
> > Toronto, ON Canada
> > .
> > <broy@.omegasoftwareinc.com> wrote in message
> > news:1150334059.199056.4380@.h76g2000cwa.googlegroups.com...
> > Thanks Tom...
> >
> > Just FMI, wasn't this something that could be done in SQL Server 2000
> > without uninstall/reinstall? Did the capability disappear with SQL
> > Server 2005 or was it never there even in 2000?
> >
>
>|||"do at your own perils" is just my blanket disclaimer when it comes to
system configuration. Actually, you can do all this very safely. Instead of
modifying the existing keys, you can create a new set. Modify this new set
with appropriate changes (I'll see about putting an article together
documenting it all). Register a new service for the new instance and then
start it.
Your original configuration/data is _never_ touched, so, if need to, you can
always start up the old instance.
--
-oj
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:97130750-F0A3-483C-8693-BAD70E02F5CF@.microsoft.com...
> The problem is that 'do at your own perils!' How does one know that all
> the
> references to the old instance name have been changed everywhere?
> Linchi
> "oj" wrote:
>> it's actually possible. (WARNING: do at your own perils!)
>> 1. drop current instname (sp_dropserver)
>> 2. add new instance name (sp_addserver 'new name','local')
>> 3. stop sqlserver
>> 4. modify hklm\software\microsoft\microsoft sql server\
>> 5. modify hklm\system\mssql$<instance>
>> 6. use "sc create" to add new mssql$<inst>
>> 7. start up with new inst_name - voila!
>>
>> --
>> -oj
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23eYqXqBkGHA.2200@.TK2MSFTNGP05.phx.gbl...
>> >I don't recall it being a possibility with 2000. However, it's been on
>> >my
>> > wish list for a good long time. Don't get me started... ;-)
>> >
>> > --
>> > Tom
>> >
>> > ----
>> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> > SQL Server MVP
>> > Toronto, ON Canada
>> > .
>> > <broy@.omegasoftwareinc.com> wrote in message
>> > news:1150334059.199056.4380@.h76g2000cwa.googlegroups.com...
>> > Thanks Tom...
>> >
>> > Just FMI, wasn't this something that could be done in SQL Server 2000
>> > without uninstall/reinstall? Did the capability disappear with SQL
>> > Server 2005 or was it never there even in 2000?
>> >
>>|||Makes you wonder why MS doesn't have a tool to do this - without the risk or
disclaimer. I think many folks would sure love to have it.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"oj" <nospam_ojngo@.home.com> wrote in message
news:O%23dBhbKkGHA.3484@.TK2MSFTNGP03.phx.gbl...
"do at your own perils" is just my blanket disclaimer when it comes to
system configuration. Actually, you can do all this very safely. Instead of
modifying the existing keys, you can create a new set. Modify this new set
with appropriate changes (I'll see about putting an article together
documenting it all). Register a new service for the new instance and then
start it.
Your original configuration/data is _never_ touched, so, if need to, you can
always start up the old instance.
--
-oj
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:97130750-F0A3-483C-8693-BAD70E02F5CF@.microsoft.com...
> The problem is that 'do at your own perils!' How does one know that all
> the
> references to the old instance name have been changed everywhere?
> Linchi
> "oj" wrote:
>> it's actually possible. (WARNING: do at your own perils!)
>> 1. drop current instname (sp_dropserver)
>> 2. add new instance name (sp_addserver 'new name','local')
>> 3. stop sqlserver
>> 4. modify hklm\software\microsoft\microsoft sql server\
>> 5. modify hklm\system\mssql$<instance>
>> 6. use "sc create" to add new mssql$<inst>
>> 7. start up with new inst_name - voila!
>>
>> --
>> -oj
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23eYqXqBkGHA.2200@.TK2MSFTNGP05.phx.gbl...
>> >I don't recall it being a possibility with 2000. However, it's been on
>> >my
>> > wish list for a good long time. Don't get me started... ;-)
>> >
>> > --
>> > Tom
>> >
>> > ----
>> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> > SQL Server MVP
>> > Toronto, ON Canada
>> > .
>> > <broy@.omegasoftwareinc.com> wrote in message
>> > news:1150334059.199056.4380@.h76g2000cwa.googlegroups.com...
>> > Thanks Tom...
>> >
>> > Just FMI, wasn't this something that could be done in SQL Server 2000
>> > without uninstall/reinstall? Did the capability disappear with SQL
>> > Server 2005 or was it never there even in 2000?
>> >
>>|||well, it's not that simple. ;-)
you can't easily change instance name if you have replication, loopback
linked server, etc. which depends on the old instance name. also, it would
be more support call for them because the new instance name does not
reference the normal instance path (i.e. physical location/pointer still
point to the old instance). this can be very confusing for _regular_ users.
uninstall/reinstall is the recommended route because it ensures everything
is right where it should be. of course this requires some work on the dba
(i.e. move data from old instance to new instance) but that's not of their
concern.
-oj
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OY4F5FNkGHA.456@.TK2MSFTNGP05.phx.gbl...
> Makes you wonder why MS doesn't have a tool to do this - without the risk
> or
> disclaimer. I think many folks would sure love to have it.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:O%23dBhbKkGHA.3484@.TK2MSFTNGP03.phx.gbl...
> "do at your own perils" is just my blanket disclaimer when it comes to
> system configuration. Actually, you can do all this very safely. Instead
> of
> modifying the existing keys, you can create a new set. Modify this new set
> with appropriate changes (I'll see about putting an article together
> documenting it all). Register a new service for the new instance and then
> start it.
> Your original configuration/data is _never_ touched, so, if need to, you
> can
> always start up the old instance.
> --
> -oj
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:97130750-F0A3-483C-8693-BAD70E02F5CF@.microsoft.com...
>> The problem is that 'do at your own perils!' How does one know that all
>> the
>> references to the old instance name have been changed everywhere?
>> Linchi
>> "oj" wrote:
>> it's actually possible. (WARNING: do at your own perils!)
>> 1. drop current instname (sp_dropserver)
>> 2. add new instance name (sp_addserver 'new name','local')
>> 3. stop sqlserver
>> 4. modify hklm\software\microsoft\microsoft sql server\
>> 5. modify hklm\system\mssql$<instance>
>> 6. use "sc create" to add new mssql$<inst>
>> 7. start up with new inst_name - voila!
>>
>> --
>> -oj
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23eYqXqBkGHA.2200@.TK2MSFTNGP05.phx.gbl...
>> >I don't recall it being a possibility with 2000. However, it's been on
>> >my
>> > wish list for a good long time. Don't get me started... ;-)
>> >
>> > --
>> > Tom
>> >
>> > ----
>> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> > SQL Server MVP
>> > Toronto, ON Canada
>> > .
>> > <broy@.omegasoftwareinc.com> wrote in message
>> > news:1150334059.199056.4380@.h76g2000cwa.googlegroups.com...
>> > Thanks Tom...
>> >
>> > Just FMI, wasn't this something that could be done in SQL Server 2000
>> > without uninstall/reinstall? Did the capability disappear with SQL
>> > Server 2005 or was it never there even in 2000?
>> >
>>
>