Archive | Shrinking & Transactions RSS feed for this section

Manage Your Transactions (So They Don’t Manage You – Part 2)

by Mike Walsh on 16. Apr, 2009 in Best Practices, Performance, Pet Peeve, SQL Server, Shrinking & Transactions, Syndicate

This is the final in a series on shrinking and transactions. You can see them all in the Shrinking & Transactions category.
In part 1, we talked about factors that affect transaction log growth. We talked about what a SQL Server transaction is and the various modes SQL interacts with a transaction (Autocommit, Implicit Transactions and Explicit [...]

  • Share/Bookmark
Read full story • Comments { 0 }

Manage Your Transactions (So they don’t manage you – Part 1)

by Mike Walsh on 09. Apr, 2009 in Best Practices, Pet Peeve, Recovery, SQL Server, Shrinking & Transactions, Syndicate

This is part 3 in a series on shrinking and transaction management. Click here for part 4. You can see them all in the Shrinking & Transactions category.
If you are one of the people who have been reading this blog, you know where I stand on shrinking databases/log files. I don’t like the practice (Post 1, Post [...]

  • Share/Bookmark
Read full story • Comments { 4 }

Shrinking is a popular topic…

by Mike Walsh on 31. Jan, 2009 in DBA, SQL Server, Shrinking & Transactions, Syndicate

This is part 2 in a series on Shrinking “Best Practices” and logging. Click here for part 3. You can see them all in the Shrinking & Transactions category.
A while back I posted about not touching the shrink button. I am still finding it fun to see what search queries bring traffic to my blog [...]

  • Share/Bookmark
Read full story • Comments { 4 }

Don’t Touch that Shrink Button!

by Mike Walsh on 07. Jan, 2009 in Best Practices, DBA, Pet Peeve, Shrinking & Transactions, Syndicate

This post is part 1 in a series on shrinking and transaction management. Part 2 is linked at the bottom or here. You can see them all in the Shrinking & Transactions category.
This topic has indeed been done to death. Yet I still often encounter unnecessary database autoshrinks, scheduled shrink jobs and at times a seeming [...]

  • Share/Bookmark
Read full story • Comments { 11 }