In this week's survey, I'm interested in how *you* manage the size of your transaction log. I'll report on the results around 4/10/2009.
Thanks!
(No comments please… wait till the results post next week)
Jonathan had a client issue recently where SQL Server’s buffer pool had been forced down to a ridiculously small size, only a few hundred MB,
(This post first appeared on SQLperformance.com four years ago as part of a blog series, before that website was mothballed later in 2022 and the
One of the easiest ways to increase query performance in SQL Server is to make sure that it can quickly access the requested data, and
Spring is already in the air here in Redmond so time for March Madness! Hundreds of dollars lower-than-ever prices on our signature 158-hour Blackbelt training
In the previous Curious Case I described an issue Jonathan had at a client with very long IAM chains, and the circumstances leading to it.
(The original version of this post first appeared on the now-deleted SentryOne blog at the start of 2022.) One of the most fundamental concepts in
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.
6 thoughts on “Weekly survey: transaction log size management”
In order to maximize performance and disk space, I’ve created a RAM Disk that I place the TX logs on. This improves performance for big maintenance jobs and I can easily free up space by rebooting the server.
Wow – that’s very scary – I hope you’re kidding…
I voted, but I’d like to put in a request for check boxes (multiple options) rather than radio buttons (single option) for this one.
Pam – unfortunately the free survey service I use doesn’t have that option – and I was near the 10 options limit so I couldn’t add in any combos. Thanks for voting though.
1. full back up ervery day
2. log back up ervery day
3. DBCC SHRINKFILE(,,TRUNCATEONLY) executed everyday
any more better suggestions?
If you’re only doing a log backup once per day, you’re looking at a potential of up to 24 hours of data loss in a disaster. That’s not usually an acceptable amount for most businesses. And don’t do the truncateonly every day. Only shrink rarely if the log has grown out of control for some reason.