February 27, 2007 at 6:47 am
All,
Just an FYI. I found out there is a problem with SP2 (big surprise there. @=) and thought I'd pass on the news in case any of you use the affected features. BTW, as far as I know, plans created by programs like Litespeed Backup are not affected, but if I find out otherwise (I use Litespeed at my office) I will post again and let you all know.
QUOTE: A serious issue has been reported against SP2 concerning database maintenance plans.
We are mainly concerned because the problem happens silently and customers may not be aware that their maintenance deletion policies have changed. Worst case this could mean that some customers are running without backups because their deletion policy changed.
We plan on posting a message on the download site tonight warning customers about this issue. Also, we have notified our marketing team who will help send out an all-points-bulletin to the field plus are engaging our community team to help us message this externally.
In the mean time, customers who notice that their plan changed can correct their plan using the SP2 tools. Therefore we are going to communicate this widely but at the moment are not recalling SP2.
February 27, 2007 at 8:53 am
Yes, this issue has been extensivly discussed in the forum over the past week.
Just wondering how Microsoft let this one slip thru?
February 27, 2007 at 9:01 am
Ah. I didn't realize someone had already posted the issue. Sorry about that.
My take on it is this is one of those things no one thought to check. After all, how often does anyone go to their backup share and look at the files and filedates as part of their daily / weekly preventative maintenance checks?
February 27, 2007 at 12:29 pm
Ideally, as an administrator, if there is any major change in the computer, you should check all the scheduled job, backup and ......
Even there is no major changes at all, you should still check such as backup result from time to time.
February 27, 2007 at 9:47 pm
There were issues before sp2... It think in sp1...
MPs file cleanup was not working properly...in continuation to that definately you have to check all major jobs after applying SPs and patches...
MohammedU
Microsoft SQL Server MVP
February 28, 2007 at 9:09 am
We do need check the backup's on a daily basis as its the back bone for dba's. We get caught in tight spot only when there are no backup's when the end user requests data.
February 28, 2007 at 10:31 am
I know a lot of people who do the Ronco thing, "Set it and forget it" when it comes to backups. The job works perfectly and the backups from the night before restores just fine to the daily "quality check" database, but none of them ever bothers to go to the file folder where the backups are stored to verify it's keeping the correct amount of backups, etc. unless the hard drive runs out of space.
It's amazing the things some people forget to check. @=) That's what makes me think that it never occurred to the MS people to check this fact until it was too late. They were worried about the stuff they knew could be a problem. But how many members of their SQL Development Team actually have to worry about backups of their system on a daily basis?
March 6, 2007 at 12:35 pm
http://bink.nu/Article9653.bink
MohammedU
Microsoft SQL Server MVP
March 6, 2007 at 12:45 pm
Thanks, Mohammed! You are a gem! @=)
March 6, 2007 at 1:19 pm
Thanks Brandie....
MohammedU
Microsoft SQL Server MVP
March 6, 2007 at 9:42 pm
Critical Update for SQL Server 2005 Service Pack 2 (KB:933508)
MohammedU
Microsoft SQL Server MVP
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply