+1 to what everyone else has echoed - great question, and unfortunately, one I missed - TGIF!

Thanks Perry - I will read through this - thanks for sharing it

Russell; I'm looking to implement something similar to this and I'd be very curious to see how you implement this (seems like a great step-by-step article that you could post...

Thanks for the information; I will check it out 🙂

2 days after-the-fact, a full check returns no errors

DBCC CHECKDB ('MYDB') WITH ALL_ERRORMSGS, NO_INFOMSGS

You maybe able to uses the sysprocesses table to determine the hostprocess ID. You can use the hostprocess ID to find the PID on the server it originated from:SELECT

...

Interesting.

On the other server where I restored the latest full/diff backup, I ran a serious of checks (including the ones you mentioned) and finished it all off with DBCC CHECKDB('SSRS')...

Thanks Gail, as always I appreciate the feedback. Yes, I tried the restart and while it resolved the CLR issues, it still comes back after running a full blown...

Interestingly enough, running this returned no errors

What exactly isn't working? Are you getting an error? Could be that one of your values in the CASE is NULL...

What's a good way to determine...

Thanks for that clarification 🙂 Appreciate it!

hiram.osiris (12/5/2013)

---

There's also a workaround that I saw once here:

1.-Stop SQL Server service from Configuration Manager

2.-Open CMD console as administrator and go to the following path: C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012(Here...

Seems about right but would strongly encourage you to verify that the anonymous/immediate_sync options have been set properly, if they are not set to 0, when you trigger the snapshot...it...

You can query the BackupSet and BackupMediaFamily tables in the msdb database:SELECT

CONVERT(CHAR(100), SERVERPROPERTY('Servername')) AS Server,

bu.database_name,

bu.backup_start_date, ...