SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


MOVE DB Online


MOVE DB Online

Author
Message
DBA12345
DBA12345
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 240
Hi

Is there any way to move DB to different location with out downtime.

It means We have to move DB online with zero downtime. This move can be different hard drive or different server.

Currently I am using sql server 2008 R2 Enterprise edition.

Thanks
Aswin
GilaMonster
GilaMonster
SSC Guru
SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)

Group: General Forum Members
Points: 86971 Visits: 45267
No.

Moving to another server can be done with minimal downtime by using log shipping or mirroring, but there will still be a small amount. Moving the DB to another drive requires that the database be offline while the file is moved.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


kevaburg
kevaburg
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1589 Visits: 988
Although it isn't possible as Gail has said with zero downtime I have done this using mirroring and I managed to complete the process extremely quickly.

What I did was:

1. Decide which server was going to host the mirror and change the connection string for the application servers to include the failover server.
2. Establish the mirror using high safety. The switchover itself would ensure zero data loss but I am a believer in high safety.
3. Perform the switchover, preferrably during a time of minimal usage on the server is possible.

There was a point for a few seconds whereby the users could not connect but it was not significant enough to cause any problems.

I would recommend though:

1. Ensure you perform the switchover at a time whereby no long running queries are active
2. Try to choose a time where the minimum connections to the database are established
3. Warn your users that there will a minimum of disruption for a short period of time.

Good luck with the move!

PS: This was done on 2005
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