Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Stairway to Transaction Log Management in SQL Server, Level 6: Managing the Log in BULK_LOGGED...


Stairway to Transaction Log Management in SQL Server, Level 6: Managing the Log in BULK_LOGGED Recovery Model

Author
Message
GilaMonster
GilaMonster
SSC Guru
SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)

Group: General Forum Members
Points: 72276 Visits: 44959
Comments posted to this topic are about the item Stairway to Transaction Log Management in SQL Server, Level 6: Managing the Log in BULK_LOGGED Recovery Model

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


paul.knibbs
paul.knibbs
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2307 Visits: 6230
I'm sure I've said this before, but I don't think the advantages of using BULK LOGGED mode are worth the potential risks. If the data is critical enough that the database is normally in FULL recovery, then IMHO it's too critical to risk losing a chunk of it. Conversely, if it ISN'T that critical, you might as well run the database in SIMPLE recovery and not bother with logs at all! Of course, this is purely an opinion, your mileage may vary, etc... :-)
Wison
Wison
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 151
Hi, in your post, you can find the data in the [Log Record] of fn_DBLog feedback.
but the string is too long.


/**
create table c (name char(5))
insert into c select 'wison'
**/

the [Log Record] of fn_DBLog related to the [LOP_INSERT_ROWS] is :
0x00003E0015000000D00000000100020063020000000002019F000000010000001E00000015000000D00000000F000001000010000000000100000000410003000C00000014004200100009007769736F6E0100000101000C00009211550000000102000402030004

how can i analysis it?
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