My database has recently suddenly increased in size from 237,985 KB to 1,685,030 KB (August 12th to 13th). The system has been working perfectly for some 8 years.
A "properties" selection on "master" gives Size 25.06 MB, Space Available 1.22 MB
A "properties" selection on "Live data" gives Size 1959.56 MB, Space Available 1559.52 MB
Every night a Maintenance Plan is executed - a log of this shows failure every day apart from 17th and 25th August! The time taken to fail is anywhere between 3 minutes and 9 minutes.
The operations carried out in this are:- Backup, Check Integrity, History Cleanup, Maintenance Cleanup,Rebuild Index, Reorganize Index, Shrink.
When it fails - everything is ticked apart from "Shrink".
I have increased the timeout value from 600 to 900 secs in case it were taking too long - however the on demand maintenance task then ran for 10m 25sec before failing.
I do have some .trc files in the Program files\Microsoft Sql Server\MSSQL.1\MSSQL\LOG which I have tried looking at but "it's all greek!"
Examination of the Maintenance plan logs (in the LOG directory above) shows that the order in which the jobs are run appears to be completely random (and concurrent). The failure message reads "backup and maintenance operations .... must be serialized" - there appears to be no means of specifying either "completion" or "order"
Anyone able to shed some light?