Something strange. It does indeed create a new file for all jobs I got. But it also adds another another jobs to the same file. What could be the case?

While backup time and size using Litespeed is cut considerably, restore time is about the same as for the native restore. I would be cautios (do a lot of testing...

run sp_who2; and see if there is blocking or old connection....

Check also all available disk space. (It is nice to have a stored proc which monitores disk space accross all servers). On one of my servers, where tempdb is on...

select db, usr, count(*) as processes from

( select sp.loginame as usr, sd.name as db

from sysprocesses sp join sysdatabases sd on sp.dbid = sd.dbid ) as db_usage

where db like('%')

group by...

Not exactly.

You could run :

EXEC master..xp_servicecontrol 'QueryState', 'SQLServerAgent' and then capture the result in temp table; and based on a response run a job. The only problem you might...

Can it be the case that your logic requires to use a lot of temp tables? Make sure they are being dropped at the end of the stored proc. Also...

Congratulations, Frank!

Can't you just create a job, with DBCC CHECKDB('MYDB')?

Make sure you create and output txt file to capture the output (on Advanced Tab)

use xp_servicecontrol.

as an alternative you can specify in the job step:Advanced->Output File(create output file on the local drive) with Overwite or Append. It saves all output (which you see in QA)...

Thanks Guys.

Yes Mike, if you can send me details....

The way we handle it:

You should have a list of servers  stored in table (and a separate table for DBs going against servrid) in standalone db on a master server....

"I've tried log shipping, but the size of the logfiles it creates is very large (>1gb), and takes a while to copy over to the secondary server, causing a large...

I have a problem with "If someone gets in and screws things up accidentally, or does it on purpose not caring if he gets caught.."

To prevent things to happen accidently,...