SQL Server Performance Forum – Threads Archive

Move SQL-Server

Env.: Win2000, SQL2000 I need to creat a server exactly like what we have in production. I took these steps: 1. Stopped SQL-Server in production. Of course when it was not in use <img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ /> 2. Coppied the E:MSSQLDATA folder to new server. This is where I have all DBs including Master, MSDB, Model. (SQL Server is installed on C: drive) 3. Start SQL-Server. As a next step, should I attach the databases to SQL-Server on new server? And replace the Master, MSDB, and Model databases with existing ones on New server? Am I on right path? Or there is a better way? Thanks, CanadaDBA

I recommend to restore in new server: master, msdb, model and database, of course if no database in new server is usefull.
If you attach database in new server, don’t forget to Update Statistics. Luis Martin
Moderator
SQL-Server-Performance.com All postings are provided â€œAS ISâ€ with no warranties for accuracy.

Would you explain more?

quote:Originally posted by LuisMartin …, of course if no database in new server is usefull.
If you attach database in new server, don’t forget to Update Statistics.

CanadaDBA

2. Coppied the E:MSSQLDATA folder to new server. This is where I have all DBs including Master, MSDB, Model. (SQL Server is installed on C: drive) I understand you allready have databases in new server.
If you restore Master, msdb and model (with old server data) you will lost those databases, I mean actual databases in new server.
If this is ok for you go on.
If you don’t want to loose those databases, then you can restore database from old to new server, in this case SQL new server have not information about statistics of that database, so you have to Update Statistics after restore database.
Same thing if you dettach in old server, copy to new and attach again. Luis Martin
Moderator
SQL-Server-Performance.com All postings are provided â€œAS ISâ€ with no warranties for accuracy.

For the user databases you can attach/detach or use the full database from productions server to restore on development server. FOr the logins refer to these articles:
http://www.databasejournal.com/features/mssql/article.php/2228611
http://www.databasejournal.com/features/mssql/article.php/2224361 For jobs and DTS packages you may wish to restore MSDB in order to get all of them.
I would never go in other way to copy the SQL server (databases) from one system to another using file copy mechanism, for the system database its better to use the defined way of BACKUP/RESTORE. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

]]>