Transaction Log Archives - Page 2 of 2

Making the Case for INSTEAD OF Triggers – Part 1

SQL Sentry's Aaron Bertrand (@AaronBertrand) does some deeper testing on triggers, showing that INSTEAD OF triggers are worth a look.

Aaron Bertrand ◆ March 25, 2014

1

Transaction Log Monitoring

Paul Randal (@PaulRandal), CEO and owner of SQLskills.com, discusses monitoring the transaction log, as he rounds out his series on transaction log configuration and management.

Paul Randal ◆ November 21, 2013

6

SQL Server 2014 : Native backup encryption

SQL Sentry's Aaron Bertrand (@AaronBertrand) takes a quick look at performance of encrypted backups in SQL Server 2014, and points out a couple of other things you'll want to know before implementing the feature.

Aaron Bertrand ◆ October 16, 2013

7

The Myth that DROP and TRUNCATE TABLE are Non-Logged

Paul Randal (@PaulRandal) of SQLskills.com discusses the myth that DROP and TRUNCATE operations are not logged, and shows that this is simply not true.

Paul Randal ◆ May 31, 2013

21

Looking at Database Snapshot Performance

Jonathan Kehayias (@SQLPoolBoy) of SQLskills.com takes a look at snapshot performance, with some surprising observations about what happens if you have more than one concurrent snapshot.

Jonathan Kehayias ◆ May 21, 2013

10

Break large delete operations into chunks

Aaron Bertrand (@AaronBertrand) discusses ways to optimize large delete operations, both to make them faster, and to minimize impact on the transaction log.

Aaron Bertrand ◆ March 13, 2013

48

Transaction Log Configuration Issues

Paul Randal of SQLskills continues his series on maintaining happy and healthy transaction logs in SQL Server, this time focusing on configuration issues that can lead to less than optimal performance.

Paul Randal ◆ February 22, 2013

8

Trimming More Transaction Log Fat

In my previous post on streamlining the operations of the transaction log, I discussed two of the most common causes of extra log records being generated: dead weight from unused nonclustered indexes and page split operations (that cause index fragmentation). Assuming you’ve read that post, I mentioned that there are more subtle problems that can be detrimental to transaction log performance, and I’m going to cover these here.

Paul Randal ◆ January 22, 2013

8

Potential enhancements to ASPState

Many people have implemented ASPState in their environment. Some people use the in-memory option (InProc), but usually I see the database option being used. There are some potential inefficiencies here that you might not notice on low volume sites but that will start to affect performance as your web volume ramps up.

Aaron Bertrand ◆ January 11, 2013

14

Trimming the Transaction Log Fat

In many SQL Server workloads, especially OLTP, the database’s transaction log can be a bottleneck that adds to the time it takes a transaction to complete. Most people assume that the I/O subsystem is the real bottleneck, with it not being able to keep up with the amount of transaction log being generated by the workload.

Paul Randal ◆ December 17, 2012

11