Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 839
  • Last Modified:

Moving SQL 2005 databases to new hardware

Hi

I've read some of the earlier questions, but none that is 100% similar to mine, as far as I can see. The case is as follows.

Old Server.- Win 2003 Server running SQL Server 32-bit
New server - Win 2008 running SQL Server 64-bit (SP2)

Both servers are in the same domain. But the thing is that the sql server contains 967 rather small databases (Not my fault, but the ERP System we're using, it creates 5 - 6 databases each year for each company we're working on --- Jeez...!)

But the backup/restore and detach/attach routines can only be used on one db at the time (??)
Will I have to move system databases, or will these be updated with the needed info during attach routine?

I have a custom script made by ERP-developer, maybe this will be the easiest to use, it creates and runs a attach scrip automatically for all 967 dbs (sic...)

Extra info: both databases is up and runnning and have sa login.
0
Jakob Digranes
Asked:
Jakob Digranes
3 Solutions
 
luaniCommented:
The database catalog will filled during the attach but if U have Jobs U have to backup and restore all the system databases.............
0
 
thiyagukTech Lead Commented:
yes. you can use attach/detach method if you don't have any jobs/replication etc.,
0
 
Jakob DigranesSenior ConsultantAuthor Commented:
This is a rather straight forward and simple SQL install.

All I've done is install it, and the ERP-system creates and maintanes the dbs. All I ever do is run backup with Symantec BE. Så i guess theres no special jobs going, and aboslutely no replication.

But will i have to detach/attach the DBs one-by-one?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
luaniCommented:
you can write a script to do that. Do you have only the ERP-related databases there? Are the databases on single files?

you can so some thing like
USE master;
--set databases in single user mode prior to detach
ALTER DATABASE db1
SET SINGLE_USER;
GO

ALTER DATABASE db2
SET SINGLE_USER;
GO
--detach
exec sp_detach_db 'db1',true
exec sp_detach_db 'db2',true

--copy mdf to the new server
--then attach this part to be executed on the new server!!!

EXEC sp_attach_db @dbname = N'db1',
   @filename1 = N'c:\db1.mdf' --or wherever this file will be

EXEC sp_attach_db @dbname = N'db2',
   @filename1 = N'c:\db2.mdf' --or wherever this file will be
0
 
St3veMaxCommented:
As long as the SQLAgent is installed on both nodes; BE can backup and then restore onto the new server. My only concern would be how long this would take to accompolish as BE is very chatty and doesent always start a backup job when you want.

Try a dummy run; perhaps restore a recent full backup to see how long it takes?

HTH
0
 
Jakob DigranesSenior ConsultantAuthor Commented:
I chose the long hard winding, but safest road. DB-Attach on all 837 DBs. The use of script last time made a mess of the where databases would be stored. And the manual attach took only a couple of hours. New server's been up and running for a week - no sweat.

0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now