I built SQL Server 2k ent sp3a on Windows 2003 ent and completed the testing
and ready to go. But we need to change the Windows server name, which means
the default instance name will be changed automatically. What's the impace
on database, or database setting or SQL server settings?
Thanks
Shouldn't be any, unless you have remote logins (e.g. for replication), or
have hard-coded the old server name in your code, or have linked servers
pointing at aliases that reference the server by its old name as opposed to
IP.
Just make sure you do:
EXEC sp_dropserver 'old name'
GO
EXEC sp_addserver 'new name', local
http://www.aspfaq.com/
(Reverse address to reply.)
"Maggie" <Maggie@.discussions.microsoft.com> wrote in message
news:6CCC918E-573C-44E5-B3C1-7733CC680A75@.microsoft.com...
> I built SQL Server 2k ent sp3a on Windows 2003 ent and completed the
testing
> and ready to go. But we need to change the Windows server name, which
means
> the default instance name will be changed automatically. What's the
impace
> on database, or database setting or SQL server settings?
> Thanks
|||also watch out for the problem with jobs as per below
http://support.microsoft.com/default...b;en-us;281642
Andy.
"Maggie" <Maggie@.discussions.microsoft.com> wrote in message
news:6CCC918E-573C-44E5-B3C1-7733CC680A75@.microsoft.com...
>I built SQL Server 2k ent sp3a on Windows 2003 ent and completed the
>testing
> and ready to go. But we need to change the Windows server name, which
> means
> the default instance name will be changed automatically. What's the
> impace
> on database, or database setting or SQL server settings?
> Thanks
No comments:
Post a Comment