September 22, 2012 at 1:43 pm
Hello,
Safety = FULL. No witness.
Principal goes down, and there's a long redo queue in mirror and will take long time to be up.
Suppose I am not worried about those logs but I just need to bring the mirror server up.
Is there any way to cancel those redo logs in mirror ? Data loss is acceptable.
Thanks,
San.
September 22, 2012 at 2:04 pm
No, it's the same as crash recovery when starting up a DB. Without there are logged changes that do not reflect in the data file, ie the database would be inconsistent without them
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
September 23, 2012 at 12:12 am
.. So ultimately I need to wait till it recovers. And time left to recover will be available in Mirror error log is it ?
By the way, a FORCE failover won't help here as well ?
Thanks Gila.
September 23, 2012 at 3:49 am
Should be.
Forcing a failover won't help, because this is not the failover process, it's the bringing of the DB online after the failover.
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
September 23, 2012 at 4:11 am
Thanks a lot Gila.
September 24, 2012 at 9:47 pm
Do I understand correctly, the same delay will happen when failing over when using clustering or log shipping?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply