Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


migration sql databaase


migration sql databaase

Author
Message
solomon.jernas
solomon.jernas
SSC-Enthusiastic
SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)SSC-Enthusiastic (188 reputation)

Group: General Forum Members
Points: 188 Visits: 979
Thank you very much for you good valuable explanation.

Thank to all..
Grant Fritchey
Grant Fritchey
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17569 Visits: 32254
I'll come right out and say it. No, it's impossible to just migrate your database over using any straight method.

I agree with the steps Hanshi laid out for a multi-step migration.

What you could do is go one step further than what Hanshi suggested and setup log shipping so that you can have, at most, maybe 2-3 minutes of downtime. You ship the 2000 server to the 2005 server, then you shut off access to the 2000 server, get the last log backup, shift that over, take the 2005 server out of log shipping and bring it online. The downtime involved is extremely minimal. If you script it very carefully (and test it to be sure), you can actually have no more than 10-15 seconds.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
Eirikur Eiriksson
Eirikur Eiriksson
SSCertifiable
SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)

Group: General Forum Members
Points: 6693 Visits: 17688
Grant Fritchey (7/9/2014)
I'll come right out and say it. No, it's impossible to just migrate your database over using any straight method.

I agree with the steps Hanshi laid out for a multi-step migration.

What you could do is go one step further than what Hanshi suggested and setup log shipping so that you can have, at most, maybe 2-3 minutes of downtime. You ship the 2000 server to the 2005 server, then you shut off access to the 2000 server, get the last log backup, shift that over, take the 2005 server out of log shipping and bring it online. The downtime involved is extremely minimal. If you script it very carefully (and test it to be sure), you can actually have no more than 10-15 seconds.


Kind of missing part of the equation here is how busy is the 2K system, what kind of role does it have (transactional, reporting etc.), how beefy is the 2K5 system, has the 2K system gone through the Upgrade Advisor (detect discontinued syntax such as dump transaction etc.), is there a normal operational maintenance window (backups etc.) on the 2K and so on and so forth. We are still guessing and speculating!

When attaching a 2K database to a 2K5 server, there is a lot of I/O and CPU load involved. My rough rule of the thumb is 1 core + 8Gb ram = 50 Gb of db file size p. minute. A very rough guesstimate though ;-) That would be about 150 core minutes, my guess is that it entirely rules out such an operation within the downtime window, which is more or less in line with what Grant said.

Without the whole picture it is still guessing, one can ask if it is possible to travel 35km in a minute. It is but it takes military grade (very expensive) hardware and yet it would need a flying start!
Cool
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search