<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>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<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
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Paul Randal
»
Transaction Log Backups
18 posts, Page 1 of 2
1
2
»»
Transaction Log Backups
Rate Topic
Display Mode
Topic Options
Author
Message
Paul Randal
Paul Randal
Posted Monday, February 08, 2010 8:51 PM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905,
Visits: 1,601
Comments posted to this topic are about the item
Transaction Log Backups
Paul Randal
CEO,
SQLskills.com
:
Check out SQLskills online training!
Blog:
www.SQLskills.com/blogs/paul
Twitter:
@PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of
TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Post #862180
ziangij
ziangij
Posted Tuesday, February 09, 2010 12:25 AM
SSCommitted
Group: General Forum Members
Last Login: Friday, May 17, 2013 2:53 AM
Points: 1,529,
Visits: 359
sad, i got this one wrong...
2 options looked very likely ...
http://msdn.microsoft.com/en-us/library/aa173551(SQL.80).aspx
Post #862238
SQLRNNR
SQLRNNR
Posted Tuesday, February 09, 2010 12:47 AM
SSCoach
Group: General Forum Members
Last Login: Monday, May 20, 2013 1:07 PM
Points: 18,733,
Visits: 12,332
Thanks Paul. Excellent question.
Jason
AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #862250
jadsmith
jadsmith
Posted Tuesday, February 09, 2010 12:49 AM
SSCrazy
Group: General Forum Members
Last Login: 2 days ago @ 2:43 AM
Points: 2,778,
Visits: 471
from sql help http://msdn.microsoft.com/en-us/library/ms186865.aspx
Under the full recovery model or bulk-logged recovery model, conventional backups also include sequential transaction log backups (or log backups), which are required. Each log backup covers the portion of the transaction log that was active when the backup was created, and it includes all log records not backed up in a previous log backup.
This indecates that the last answer is correct.
Also it would need to backup anything not backed up in a previous log backup so that it could restore to a point in time after the last log backup.
Post #862252
jshailendra
jshailendra
Posted Tuesday, February 09, 2010 1:13 AM
Old Hand
Group: General Forum Members
Last Login: Friday, December 21, 2012 5:24 AM
Points: 366,
Visits: 436
Good question..simple one if basics are clear...
Post #862257
Stewart "Arturius" Campbell
Stewart "Arturius" Campbell
Posted Tuesday, February 09, 2010 5:28 AM
Hall of Fame
Group: General Forum Members
Last Login: Monday, May 20, 2013 3:48 AM
Points: 3,125,
Visits: 4,311
Good question
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
Post #862345
john.curran.z3g
john.curran.z3g
Posted Tuesday, February 09, 2010 6:35 AM
SSC Veteran
Group: General Forum Members
Last Login: Monday, February 18, 2013 7:25 AM
Points: 236,
Visits: 53
This page suggests that option 2 is correct:
http://msdn.microsoft.com/en-us/library/ms186289.aspx
You can re-create a whole database in one step by restoring the database from a full database backup to any location. Enough of the transaction log is included in the backup to let you recover the database to the time when the backup finished.
Post #862378
sjimmo
sjimmo
Posted Tuesday, February 09, 2010 6:35 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 7:15 AM
Points: 2,864,
Visits: 2,467
Great question - got it wrong, but caused me to think.
Steve Jimmo
Sr DBA
“If we ever forget that we are One Nation Under God, then we will be a Nation gone under." - Ronald Reagan
Post #862380
Lynn Pettis
Lynn Pettis
Posted Tuesday, February 09, 2010 6:46 AM
SSC-Insane
Group: General Forum Members
Last Login: Yesterday @ 11:17 PM
Points: 21,617,
Visits: 27,450
Good question. Easy if you understand recovery models and backup/restore processes.
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #862389
Paul Randal
Paul Randal
Posted Tuesday, February 09, 2010 8:23 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905,
Visits: 1,601
@jadsmith But the question wasn't about log backups - it was about full backups. Full backups do not affect log backups, nor do they take them into account. A full backup only has to include the transaction log necessary to recover the database consistently to the time when the data-reading portion of the backup completed. It doesn't matter if the transaction log is GBs and there hasn't been a log backup for weeks - the full backup doesn't backup log it doesn't need.
Only a log backup will backup all log generated since the last log backup completes. And only a log backup in the FULL or BULK_LOGGED recovery models will allow the log to clear/truncate.
@john.curran.z3g That wouldn't be enough to recover the database. If there was a long running transaction that started before the full backup did, only backing up the transaction log generated during the backup would not allow the transaction to be rolled back correctly during the restore operation. All the transaction log for that transaction, all the way back to the initial LOP_BEGIN_XACT log record must be backed up for recovery to be able to operate correctly.
See my article in TechNet Magazine for a more full explanation:
Understanding SQL Server Backups
and also this blog post which gives you code examples you can use to convince yourself of what's going on under the covers:
Misconceptions around the log and log backups: how to convince yourself
Thanks
Paul Randal
CEO,
SQLskills.com
:
Check out SQLskills online training!
Blog:
www.SQLskills.com/blogs/paul
Twitter:
@PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of
TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Post #862470
« Prev Topic
|
Next Topic »
18 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
