Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Stairway to Transaction Log Management in SQL Server, Level 6: Managing the Log in BULK_LOGGED Recovery Model Expand / Collapse
Posted Friday, October 26, 2012 8:56 AM



Group: General Forum Members
Last Login: Today @ 5:18 AM
Points: 45,619, Visits: 44,147
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

Post #1377652
Posted Wednesday, November 7, 2012 2:18 AM


Group: General Forum Members
Last Login: Friday, October 14, 2016 2:57 AM
Points: 1,833, Visits: 6,210
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...
Post #1381837
Posted Tuesday, July 16, 2013 8:30 PM


Group: General Forum Members
Last Login: Wednesday, May 20, 2015 11:56 PM
Points: 23, 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 :

how can i analysis it?

Post #1474352
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse