SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Bulk Logged recovery model


Bulk Logged recovery model

Author
Message
M&M
M&M
SSCertifiable
SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)

Group: General Forum Members
Points: 5811 Visits: 3913
Sorry for the confusion. The question and answer was meant to test your knowledge on the log file backup size only and not the log file. Somehow the wording was not perfect thereby leading to wrong interpretation. Hope this clarifies.

M&M
Tom Thomson
Tom Thomson
One Orange Chip
One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)

Group: General Forum Members
Points: 25036 Visits: 12484
mohammed moinudheen (4/16/2012)
Sorry for the confusion. The question and answer was meant to test your knowledge on the log file backup size only and not the log file. Somehow the wording was not perfect thereby leading to wrong interpretation. Hope this clarifies.
.
Don't worry. Writing questions is very difficult - everyone answering expects perfection, but no-one writing questions is perfect (certainly the ones I've written have been imperfect!). Just keep producing questions, they are very welcome even when we moan about them. We are all grateful to people like you who take the trouble to write questions - after all, most people can't be bothered to try writing them.

Tom

M&M
M&M
SSCertifiable
SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)

Group: General Forum Members
Points: 5811 Visits: 3913
L' Eomot Inversé (4/16/2012)
mohammed moinudheen (4/16/2012)
Sorry for the confusion. The question and answer was meant to test your knowledge on the log file backup size only and not the log file. Somehow the wording was not perfect thereby leading to wrong interpretation. Hope this clarifies.
.
Don't worry. Writing questions is very difficult - everyone answering expects perfection, but no-one writing questions is perfect (certainly the ones I've written have been imperfect!). Just keep producing questions, they are very welcome even when we moan about them. We are all grateful to people like you who take the trouble to write questions - after all, most people can't be bothered to try writing them.


Thank you Sir.

M&M
sknox
sknox
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3887 Visits: 2919
call.copse (4/16/2012)
I would go further than the other posters on this thread - sorry, this question and the answer given are just plain WRONG.

See this MSDN blog entry which clearly explains log sizes in different modes:
http://blogs.msdn.com/b/suhde/archive/2010/12/29/transaction-log-backup-size-in-bulk-logged-recovery-model.aspx

The LOG FILE BACKUP is certainly likely to be larger.

The LOG FILE (subsequent to backup) is almost certainly SMALLER given that it is not doing point in time restore.

I will accept that the question could have been mangled unintentionally in the editorial prcess or something - but, the fact remains, the correct answer to the question as written is NO.


I would say that since the question read "...could you see a log file bigger than usual?" the only logical answer is yes. While the bulk-logged recovery model is a feature designed to reduce log file growth, it does not constrain log file growth. Therefore you certainly could see a larger log file in some circumstances.

However, I would also say that that does not seem to be the intent of the question. The question was poorly worded, but the explanation is correct. So, poor wording of the question has given us a "If False then True" situation -- which, if my memory of basic logic serves me properly, is still True. So much for logic.
mtassin
mtassin
SSCertifiable
SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)

Group: General Forum Members
Points: 7008 Visits: 72521
The CosmicTrickster (4/15/2012)
"Now, after you take a log backup, could you see a log file bigger than usual?"

No points for me. I perceive there being a difference between a "backup file" and a "log file". If someone says "log file" to me, I take it to mean the transaction log file, not the backup.



I saw could... Could you see a larger backup file.... the correct answer... well it depends... did those bulk activities you forsaw actually occur? Was there a larger amount of normal database traffic that might have caused the log file to grow? Did somebody decide to rebuild all the indexes in the database?

I mean really... Could that file, or the backup, or whatever have grown? Sure....



--Mark Tassin
MCITP - SQL Server DBA
Proud member of the Anti-RBAR alliance.
For help with Performance click this link
For tips on how to post your problems
call.copse
call.copse
SSCertifiable
SSCertifiable (5.5K reputation)SSCertifiable (5.5K reputation)SSCertifiable (5.5K reputation)SSCertifiable (5.5K reputation)SSCertifiable (5.5K reputation)SSCertifiable (5.5K reputation)SSCertifiable (5.5K reputation)SSCertifiable (5.5K reputation)

Group: General Forum Members
Points: 5492 Visits: 2005
sknox (4/16/2012)
call.copse (4/16/2012)
I would go further than the other posters on this thread - sorry, this question and the answer given are just plain WRONG.

See this MSDN blog entry which clearly explains log sizes in different modes:
http://blogs.msdn.com/b/suhde/archive/2010/12/29/transaction-log-backup-size-in-bulk-logged-recovery-model.aspx

The LOG FILE BACKUP is certainly likely to be larger.

The LOG FILE (subsequent to backup) is almost certainly SMALLER given that it is not doing point in time restore.

I will accept that the question could have been mangled unintentionally in the editorial prcess or something - but, the fact remains, the correct answer to the question as written is NO.


I would say that since the question read "...could you see a log file bigger than usual?" the only logical answer is yes. While the bulk-logged recovery model is a feature designed to reduce log file growth, it does not constrain log file growth. Therefore you certainly could see a larger log file in some circumstances.

However, I would also say that that does not seem to be the intent of the question. The question was poorly worded, but the explanation is correct. So, poor wording of the question has given us a "If False then True" situation -- which, if my memory of basic logic serves me properly, is still True. So much for logic.


I disagree. There are no circumstances where immediately post log backup, a full recovery model database log file will be less big than a bulk logged model database log file after the same set of transactions. I am pretty sure there are few conceivable circumstances where it might even be the same size. The blog link I sent above explains this pretty well.

@Mohammed
I'll echo Tom - I was pretty annoyed to spend time trying to get the question right according to the exact wording and find I still had it wrong - but I have not yet submitted any questions, so good on you. It must not be easy to put yourself before an audience who are by nature likely to be EXTREMELY pedantic.
M&M
M&M
SSCertifiable
SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)

Group: General Forum Members
Points: 5811 Visits: 3913

@Mohammed
I'll echo Tom - I was pretty annoyed to spend time trying to get the question right according to the exact wording and find I still had it wrong - but I have not yet submitted any questions, so good on you. It must not be easy to put yourself before an audience who are by nature likely to be EXTREMELY pedantic.


No problem, thank you for the feedback.

M&M
KarenM
KarenM
Old Hand
Old Hand (330 reputation)Old Hand (330 reputation)Old Hand (330 reputation)Old Hand (330 reputation)Old Hand (330 reputation)Old Hand (330 reputation)Old Hand (330 reputation)Old Hand (330 reputation)

Group: General Forum Members
Points: 330 Visits: 524
Thomas Abraham (4/16/2012)
Thank you for the question. I thought the question was straightforward, but then it's Monday.


I figured what was being asked, no confusion here either...



OzYbOi d(-_-)b
OzYbOi d(-_-)b
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1684 Visits: 778
call.copse (4/16/2012)
I would go further than the other posters on this thread - sorry, this question and the answer given are just plain WRONG.

See this MSDN blog entry which clearly explains log sizes in different modes:
http://blogs.msdn.com/b/suhde/archive/2010/12/29/transaction-log-backup-size-in-bulk-logged-recovery-model.aspx

The LOG FILE BACKUP is certainly likely to be larger.

The LOG FILE (subsequent to backup) is almost certainly SMALLER given that it is not doing point in time restore.

I will accept that the question could have been mangled unintentionally in the editorial prcess or something - but, the fact remains, the correct answer to the question as written is NO.


Tks for the question, however, I am another who answered based on log file and not log file backup... Pinch
GP Van Eron
GP Van Eron
Hall of Fame
Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)

Group: General Forum Members
Points: 3554 Visits: 471
I was also thrown off my the 'log file' at the end of the question. It should have been 'could you see a log backup file larger than usual' By Log File I thought the question meant 'transaction log file' , which immediately after a backup either in Full or Bulk-logged should be the same.

Thanks
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search