Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

MOVE DB Online Expand / Collapse
Posted Friday, September 20, 2013 3:29 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, April 24, 2014 8:19 PM
Points: 56, Visits: 240

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.

Post #1497057
Posted Friday, September 20, 2013 5:03 PM



Group: General Forum Members
Last Login: Saturday, December 3, 2016 5:18 AM
Points: 45,619, Visits: 44,147

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

Post #1497081
Posted Wednesday, September 25, 2013 5:48 AM


Group: General Forum Members
Last Login: Today @ 1:13 AM
Points: 437, Visits: 809
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
Post #1498271
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse