Finding a transaction in the log for a particular user
In the last IEHADR class we just had in Chicago, I was doing a demo of looking in the transaction log to find the point at which a table was dropped so a restore could be performed (as described in...
View ArticleClik here to view.
T-SQL Tuesday #67 – monitoring log activity with Extended Events
On the second Tuesday of each month, many people in the SQL Server community join together to all blog on the same topic – a cool idea from Adam Machanic many years ago. This month’s topic is Extended...
View ArticleCode to analyze the transaction hierarchy in the log
Over the weekend there was a discussion on the MVP distribution list about the sys.dm_tran_database_transactions DMV and how one cannot use it to accurately determine how much log an operation has...
View ArticleGetting a history of database snapshot creation
Earlier today someone asked on the #sqlhelp Twitter alias if there is a history of database snapshot creation anywhere, apart from scouring the error logs. There isn’t, unfortunately, but you can dig...
View ArticleCode to show rolled back transactions after a crash
In Monday’s Insider newsletter I discussed an email question I’d been sent about how to identify the transactions that had rolled back because of a crash, and I said I’d blog some code to do it. First...
View ArticleSQLskills SQL101: Switching recovery models
As Kimberly blogged about recently, SQLskills is embarking on a new initiative to blog about basic topics, which we’re calling SQL101. We’ll all be blogging about things that we often see done...
View ArticleSQLskills SQL101: Should you kill that long-running transaction?
As Kimberly blogged about earlier this year, SQLskills has an ongoing initiative to blog about basic topics, which we’re calling SQL101. We’re all blogging about things that we often see done...
View Article2012/2014 bug that can cause database or server to go offline
Over the years I’ve discussed log space reservation, which is when SQL Server automatically reserves some free space in the transaction log so that in-flight transactions can always be rolled back...
View ArticleSQLskills SQL101: Is the recovery interval guaranteed?
SQLskills has an ongoing initiative to blog about basic topics, which we’re calling SQL101. We’re all blogging about things that we often see done incorrectly, technologies used the wrong way, or where...
View ArticleNew VLF status value
At least since I started working on the SQL Server team (just after 7.0 shipped) and since then there have only been two VLF status codes: 0 = the VLF is not active (i.e. it can be (re)activated and...
View ArticleLazy log truncation or why VLFs might stay at status 2 after log clearing
Earlier this year I was sent an interesting question about why the person was seeing lots of VLFs in the log with status = 2 (which means ‘active’) after clearing (also known as ‘truncating’) the log...
View ArticleThe Curious Case of… faster disks causing more WRITELOG waits
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more frequent. It covers something interesting one of us...
View ArticleThe Curious Case of… why the transaction log has to be zero-initialized
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more frequent. It covers something interesting one of us...
View ArticleThe Curious Case of… too few log records for an offline index rebuild
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more frequent. It covers something interesting one of us...
View ArticleThe Curious Case of… why a minimally-logged operation doesn’t make a log...
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more frequent. It covers something interesting one of us...
View ArticleThe Curious Case of… a truncated log file after a revert from snapshot
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more frequent. It covers something interesting one of us...
View ArticleThe Curious Case of… the aborted xdes map
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more frequent. It covers something interesting one of us...
View ArticleBug: database/server ‘shutdown due to error 3314’
[Edit 3/12/2019: it looks like this bug, or a similar one, is also in SQL Server 2016. I’ll post an update once I have it.] [Edit 1/20/2020: still in 2016 SP2 CU8 as of today.] Over the years I’ve...
View ArticleSQLskills SQL101: Is the recovery interval guaranteed?
SQLskills has an ongoing initiative to blog about basic topics, which we’re calling SQL101. We’re all blogging about things that we often see done incorrectly, technologies used the wrong way, or where...
View ArticleNew VLF status value
At least since I started working on the SQL Server team (just after 7.0 shipped) and since then there have only been two VLF status codes: 0 = the VLF is not active (i.e. it can be (re)activated and...
View Article