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)
Happy Fourth of July to all who celebrate! I’m looking forward to a great view Thursday evening looking west along the Skagit Valley with some
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
We’ve added the ability to purchase a self-service health check using a credit card – no more waiting for a scoping call and then budget
Hello, my name is Paul, and I’m a high-functioning alcoholic. For the last ten years or so, I’ve been an alcoholic. A maintenance drinker –
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.