December 4, 2007 at 12:17 pm
Hi...
I have a number of database servers (SQL 2k5 9.0.3159) that keep losing there selected databases in the transaction log Maintenance Plan.
This is only happening with SQL 2005. I wouldn't worry about it too much and just chalk it up to a SQL querk/feature, but this is starting to annoy me as it usually happens when my team and I are on call. After creating the M plan and enabling it, the plan works happily for a random period of time and then just stops backing up the logs. The job still succeeds however (so no page), and when you look in the m plan and job logs, it says it started, as it should and then finished in about 2 seconds.
In the testing I have done I open up the plan and find that there are no databases selected. I reselect them and sometimes they stay there and sometimes they don't. I have also recreated the plan and it seams to stick for a while, but surely it doesn't need to be this hard.
Does anyone else have this issue or know how to resolve it?
Thanks
December 4, 2007 at 1:28 pm
I've come across similar behaviour on our dev servers. I've had strange behaviour with integrity checks as well - the scheduled job fails but there's no indication why other than 'package failed to execute'. Running manually goes fine and the next scheduled time
I'm almost at the point where I'm going to chuck the inbuilt maintenance plan stuff & put in my own stuff - it seems that whenever there is an error, the log has SFA (that's sweet all) to tell me, other than 'package failed to execute'.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
December 6, 2007 at 10:46 am
I have experience this first hand and it is very annoying. I am interested to know if anyone has discovered a fix.
-Adam
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply