InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 07:55:39 GMT20http://www.sqlservercentral.com/Forums/Topic1363166-146-1.aspxDo I understand correctly, the same delay will happen when failing over when using clustering or log shipping?Mon, 24 Sep 2012 21:47:19 GMTArjen Kraphttp://www.sqlservercentral.com/Forums/Topic1363166-146-1.aspxThanks a lot Gila.Sun, 23 Sep 2012 04:11:10 GMTJoy Smith Sanhttp://www.sqlservercentral.com/Forums/Topic1363166-146-1.aspxShould 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.Sun, 23 Sep 2012 03:49:31 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1363166-146-1.aspx.. 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.Sun, 23 Sep 2012 00:12:41 GMTJoy Smith Sanhttp://www.sqlservercentral.com/Forums/Topic1363166-146-1.aspxNo, 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 themSat, 22 Sep 2012 14:04:41 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1363166-146-1.aspxHello,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.Sat, 22 Sep 2012 13:43:36 GMTJoy Smith San