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!
Check It Out!
(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)
As you may know, anyone who attends one of our courses or self-certifies that they’ve completed watching a purchased course can get a ‘certification badge’
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 –
During the PASS Summit last week in Seattle I made a deal with my precon attendees that I’d record a couple of the demos in
AI is obviously the hot new thing and prognostications for the future range from the unicorns-and-rainbows life of idleness for us all to the post-apocalyptic
(This was the editorial for my 300th SQLskills Insider newsletter last week, that I’ve been producing since March 2011! See bottom of browser window to
I’m excited to be presenting at the Pass Summit in November! My pre-con workshop is my absolute favorite to teach Performance Tuning with Waits and
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.