To rename the server in SQL, do:
Sp_dropserver <old_name>
Go
Sp_addserver <new_name>
Go
----------------------------
Jay Zach
NT Administrator
Office (317)355-9706
[Email address protected]
----------------------------
-----Original Message-----
From: Jeff Metcalf
[mailto:mssqldba-ezmlmshield-x42991283.[Email address protected]
Sent: Wednesday, May 31, 2006 1:41 PM
To: LazyDBA Discussion
Subject: RE: Server to Server Migration
Well hoss...welcome to Microsoft's world of shoulda coulda woulda, lol.
I would guess that that info is carried over with the master db? I
don't know the specific techno weenie stuff. With SQL 2000 I don't
remember having to specify an instance on the install. Sorry I can't be
more help.
Thank you,
Jeff Metcalf
ComputerPlus Sales & Service
(864) 801 9003 ext 2016
Kindness is the language which the deaf can hear and the blind can see.
- Mark Twain
-----Original Message-----
From: Michael Phillips
[mailto:mssqldba-ezmlmshield-x22615320.[Email address protected]
Sent: Wednesday, May 31, 2006 1:29 PM
To: LazyDBA Discussion
Subject: RE: Server to Server Migration
Jeff/David,
The copy/server-rename method does seem the most promising. However, I
notice that using this method you don't seem to ever specify to rename
the SQL Server db instance, but when installing SQL Server you do have
to provide an instance name of some sort. Somehow I have to get this
instance name to end up the same as the old. If I use the same instance
name of the old server when I install SQL Server, won't that cause
problems with applications that don't use the \\servername\instance
connection syntax? (the last time I asked this question the answer was
that "it shoudn't," but I'd prefer a "it won't!")
In the end my new server and instance names must be registered exactly
as they were or my applications will fail. I like this "copy" method,
however I'm not seeing how to get the instance name/registration ending
up the same.
Michael Phillips
[Email address protected]
-----Original Message-----
From: David Brough DAB5850 [mailto:David.[Email address protected]
Sent: Wednesday, May 31, 2006 7:40 AM
To: Michael Phillips
Subject: RE: Server to Server Migration
**A LazyDBA.com subscriber has responded to your lazydba.com post**
**LazyDBA.com mail shield has forwarded you this email, **and removed
any attachments, and kept your email address secret **from this person,
and any viruses/trojans.
**If you reply to this email, the person will see your email address as
normal **Anything below this line is the original email text
We have done this several times with complete success. Here are the
steps we usually follow
1) Create the new server and install windows and SQL server (names do
not have to be the same for now)
1.1) Ensure that SQL server is installed in the same directory
structure on both machines (primarily master)
2) Create drives and folders identical to the old machine
2.1) We use a folder called SQLdata on each drive to make this
easier
3) Stop SQL server on the old and new boxes
3.1) Set SQL server and associated processes to manual startup
4) Copy the 2 master data files to the same location on the new box
5) Copy the files for the MSDB database to the same location
6) Copy the SQLdata folders from each drive to the same drive on the new
machine
7) Remove the old server from the domain, rename it to xx_OLD
8) Rename the new server and join the domain
8.1) This will require a reboot
9) Start SQL server on the new machine
10) Check the databases, assuming that your file structure moved over
correctly, they will all start normally
11) Set SQL Server and associated processes to automatic startup
12) Make sure that the new IP address for the server has been propagated
out everywhere
The nice thing about this is that you get a new install of windows and
SQL, which you do not get if you back up and restore the entire machine.
David Brough
Software Development Architect
-----Original Message-----
From: Michael Phillips
[Email address protected]
Sent: Tuesday, May 30, 2006 4:11 PM
To: LazyDBA Discussion
Subject: Server to Server Migration
I'm looking for the best overall SQL Server hardware upgrade
methodology. We need to move an instance of SQL Server from an old
server to a new one with minimal downtime. However, due to limitations
of our third party software which uses the SQL Server as a back-end,
both the server name and instance name must be the same on the new
server. Everything must be copied over, from security, views and stored
procedures to backup schedules and replication configuration.
I've read about several different approaches for doing this, but none of
them are very simple. I'm looking for the LAZY (as in LazyDBA) way.
What is the most acceptable way to do this?
Michael Phillips
Cardiac Science
[Email address protected]
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website :
http://www.LazyDBA.com To unsubscribe:
http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website :
http://www.LazyDBA.com To unsubscribe:
http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
MS Sql Server LazyDBA home page