Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kdfarber
Starting Member
24 Posts |
Posted - 2004-06-30 : 09:41:54
|
| We are in the process of moving our servers to a new datacenter and our big databases have been moved to a SAN. So, the current set up is a box with Sql server 2000 sp3a with storage attached to SAN. We are installing SQL on a new box and the data has been replicated, using EMC replication, to a SAN in new datacenter. The new box has been built with the same drive mappings. My question is when I install SQL on new box how is SQL server going to know that it already has databases and they are attached to the SAN?? Will I do the attach command ? Any input is greatly appreciated. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-06-30 : 13:16:15
|
| Here's what we've done and I'm also doing in July for a similar situation.We've got the F drive on the database servers which is where the database files are stored. On the new server, I have the server guys present a blank F drive so that I can do the installation and not overwrite anything. I then stop the SQL Services, have them unpresent this F drive and then present the F drive that contains the files from the old server. I then start up the SQL services and everything is where it should be. I even get the logins and jobs and everything else in the system databases since those were on F.Tara |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-30 : 18:17:40
|
| We do the same think. We:1. Stop SQL Server on the destination server.2. Dismount the drives.3. Clone the LUNs.4. Break the clone group.5. Mount the drives.6. Start up SQL Server.7. Attach the Databases (You only have to do this one time if you would use it for cloning.)8. Apply permissions.It works well this way.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
|
|
|