Anyone have any experience with cloning servers that have sql server
installed. I am wondering what will happen when the new virtual server comes
up using a different name. sql server takes it name from the server name.
Will it just automatically adjust or is there a process to deal with that?
Thanks.
If it's SQL Server 2005 and it has never run after installation, it will
"fix" itself upon first startup. Else, it's a simple process to
drop/register the new server name (just like in 2000). If you have other
objects in there name/server dependencies, well, that gets a little more
complicated.
joe.
"jason" <jason@.discussions.microsoft.com> wrote in message
news:68DB416E-E2B6-4E21-996C-2A99B37D6C01@.microsoft.com...
> Anyone have any experience with cloning servers that have sql server
> installed. I am wondering what will happen when the new virtual server
> comes
> up using a different name. sql server takes it name from the server name.
> Will it just automatically adjust or is there a process to deal with that?
> Thanks.
>
|||Hello Jason,
If you rename a server with SQL 2000/2005 installed, you may want to use
sp_dropserver to drop old server name, and then run sp_addserver to add the
new server name.
303774BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/default.aspx?scid=kb;EN-US;303774
317241Renaming a host computer for SQL Server causes stored procedure
debug to fail
http://support.microsoft.com/default.aspx?scid=kb;EN-US;317241
281642PRB: Error 14274 Occurs When You Update a SQL Agent Job After
Renaming Windows Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;281642
Please let me know if you have any comments or questions. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment