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)
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)
We’re tremendously excited to be developing a library of AI-focused courses, as well as new courses focused on traditional SQL Server topics, all based on
From now until mid-December we have our lowest prices ever on our signature 158-hour Blackbelt training bundle: US$1,599 for Lifetime access (no expiration) US$899 for
It’s been a while since I wrote one of these, but I’m picking up the series again. This is a question that came in through
Back in 2009 I started posting a summary at the end of the year of what I read during the year and people have been
(Yes, this is for last year!) Back in 2009 I started posting a summary at the end of the year of what I read during
It’s the time of year again where companies do crazy sales on the day after Thanksgiving in the US, and we’re doing the same! All
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.