October 1, 2012 at 9:16 am
The server in question does not have any snapshots or hidden DBs. The DBCC task that runs prior to this looks for databases that are offline or unavailable. If this task finds a db in an unstable state, it is logged in a table and that database is skipped during the backup portion.
We are changing this to run by database_id and will let it run its course this evening.
Thanks
October 1, 2012 at 9:22 am
SQLSrvrN00b (10/1/2012)
The server in question does not have any snapshots or hidden DBs. The DBCC task that runs prior to this looks for databases that are offline or unavailable. If this task finds a db in an unstable state, it is logged in a table and that database is skipped during the backup portion.We are changing this to run by database_id and will let it run its course this evening.
Thanks
The integrity check (DBCC CHECKDB) creates a temporary hidden database snapshot to perform the integrity check. If that is not getting removed immediately following the integrity check task - it could possibly be available to your script and you could end up trying to back it up.
Issues like this - generally - end up being related to the code that is being run. If you were running the built-in tasks and this was happening, it would be a bug in those tasks and could be fixed with a service pack or update. Since this is code you have written - it will need to be corrected on your side.
If you are not returning an error for a particular condition - that would make your script (and the task) appear to be successful without actually performing the work.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply