High availability best practice?

Click here to monitor SSC

<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>

SQLServerCentral is supported by Red Gate Software Ltd.

Log in :: Register :: Not logged in

<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>

Recent Posts

Popular Topics

Home

Home » SQL Server 2008 » SQL Server 2008 High Availability » High availability best practice?

Add to briefcase

11 posts, Page 2 of 2

««1 2

High availability best practice?

Expand / Collapse

Author

Message

Posted Wednesday, December 12, 2012 12:54 AM

SSC Journeyman

Group: General Forum Members
Last Login: Thursday, May 16, 2013 10:05 PM
Points: 99, Visits: 98

No it doesn't break the log chain. A full backup contains only enough transaction log necessary to be able to restore that database to a transactionally consistent time - the time at which the data reading portion of the full backup completed.

Paul has explained this very clearly in his blog.

Read the gail link above.

Regards,
RamaSankar,
MCTS,MCITP Sql Server 2008.

Post #1395478

« Prev Topic | Next Topic »

Add to briefcase

11 posts, Page 2 of 2

««1 2

Permissions

Expand / Collapse