Ok, that'll work . . . but what about SP's? With user accounts you can
do a user move in DTS on, but I guess there are other things that you
may want to have from master. I'm unsure.
Steve L. Mann
Systems Administrator I - Database Administrator
University Medical Center
Office - 520-694-4705
Pager - 520-694-4480 9278
Email - [Email address protected]
Epage - [Email address protected] Internal
Epage - [Email address protected] External
CONFIDENTIALITY NOTICE
This message and any included attachments are from University Medical
Center Corp and are intended only for the addressee. The information
contained in this message is confidential and may constitute inside or
non-public information under international, federal, or state laws and
is intended only for the use of the addressee. Unauthorized forwarding,
copying, printing, distributing, or using such information is strictly
prohibited and may be unlawful. If you are not the addressee, please
promptly delete this message and notify the sender of the delivery error
by e-mail or you may call University Medical Center in Tucson, Arizona,
USA at (+1) (520) 694-6417.
-----Original Message-----
From: Henry Jackson [mailto:[Email address protected]
Sent: Friday, November 30, 2007 8:33 AM
To: Mann, Steve L.
Subject: RE: moving master DB from one server to another
**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
I have found (the hard way) that the only system database that should be
moved to another server is MSDB. If you restore the associated user
databases, you will get the same affect. Just make sure the instance is
created with the same sort order and you will be fine.
Henry L. Jackson
Scalability Experts
Senior Consultant
[Email address protected] [Email address protected]
Office: 469.635.6200
Microsoft's 2005 Global Award of Excellence Winner: Advanced
Infrastructure Solutions/ Data Management & Consolidation
Check out SQLscaler 2.0
<https://mail.scalabilityexperts.com/exchweb/bin/redir.asp?URL=http://ww
w.scalabilityexperts.com/default.asp?action=article%26ID=377> - The SQL
Server scalability and performance testing tool designed and developed
by Scalability Experts
________________________________
From: Mann Steve L. [Email address protected]
Sent: Thu 11/29/2007 6:37 PM
To: LazyDBA Discussion
Subject: moving master DB from one server to another
Hello all,
I have a question about moving the Master database from one
server to another where the disk structure is different. (i.e. I'm
moving from d:\mssql\data\ to e:\mssql\data)
Basically, I created a SQL Server on a new server, updated
it to the same version (8.00.818) . . . but I can't start up the server
after restoring the master DB from the old server.
Now, I know to stop the server, go to cmd line and run
sqlservr -c -m from the binn directory . . . then in query analyzer, I
run the restore with move command . . . which works . . . But when I
try to start it back up, nothing . . . I gather that the main reason is
because the master DB holds the database location information and that
has changed (which is not fixed by the 'with move' command). . .
How can I fix the following script to restore it? Or is
there something else I need to do that I'm not doing?
RESTORE DATABASE master
FROM DISK = 'c:\SQLBKP\Masterbkp.bak'
WITH MOVE 'master' TO 'e:\MSSQL\data\master.mdf',
MOVE 'mastlog' TO 'e:\MSSQL\data\mastlog.ldf',
REPLACE,
STATS = 10
Thanks! (grin)
Steve
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com <http://jobs.lazydba.com/>
To subscribe : http://www.LazyDBA.com <http://www.lazydba.com/>
To unsubscribe: http://www.lazydba.com/unsubscribe.html
MS Sql Server LazyDBA home page