Comments
Sort by recent activity
This is a pretty severe limitation as it assumes a database hasn't been created, moved, taken offline, changed recovery model, put in single user mode or any number of other possibilities that could cause an error. So, for a server with, let's say more than a dozen or so databases I have to constantly monitor and adjust my backup jobs. Please add this to your feature request list. / comments
This is a pretty severe limitation as it assumes a database hasn't been created, moved, taken offline, changed recovery model, put in single user mode or any number of other possibilities that coul...
Thanks Marianne. I'll give that a try. One more question - can I pass in a TSQL like variable for the database name so I don't have to maintain a hard coded list of databases to backup or exclude? I'm not finding that addressed in the documentation. / comments
Thanks Marianne. I'll give that a try. One more question - can I pass in a TSQL like variable for the database name so I don't have to maintain a hard coded list of databases to backup or exclude...
Can't believe this tool is flooding my SQL Server error logs with DBCC TraceON and DBCC TraceOff msgs. Is there some way to stop this from cluttering my error logs? / comments
Can't believe this tool is flooding my SQL Server error logs with DBCC TraceON and DBCC TraceOff msgs. Is there some way to stop this from cluttering my error logs?