Why not use SSMS to detach then re-attach (remember to delete the log on the attach dialog) ? Or attach the .mdb to a new SQL instance?

I think that this...

If you are running SQL2K8 why not look at the SQL Server Audit? Not sure if this would met all your requirements but I'd be reluctant to use traces....

1) SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\MSSQL\Data\XXXX.mdf] in database

----------------------------------------

I had this when before my disk failed....

what logins do you use for SSMS/rdc?

I think that we can rule out TDE in your case, as it will make data visible to someone who has login permissions. Encrypting columns will work but there could...

How well does this scale? If I have thousands of users hitting the server...

If I'm right, the scale issue will very often not be picked up during testing but only...

Glenn,

thanks for your solution.

Looks pretty close to what I did.

thing is, I shouldn't have had to do this - I already had Red Gate backups of msdb. Should have been...

hi

Thanks for the reply

This is on a virtual machine. We moved the filestore whilst the database was on-line, which seems to have caused major issues - but only on MSDB.

Looks...

Know this is late but I thought I'd document my fix for this.

Open IIS and browse ReportServer. This gives an indication of the problem.

In my case, the C:\Program Files\Microsoft SQL...

is the database in Simple or full recovery?

why not have two extra steps - one for good end and one for failure?

Your 'normal' processing will complete and move to the good end step. this e-mails completion.

If there...

backup with truncate will break your restore chain - probably not what you should do?

the backup will not shrink the log.

You will have to do this yourself - dbcc shrinkfile or use ssms.

make sure to leave space in the log for normal growth

"In my case most of them are 1 which is good."

I think you will have to make sure that ALL the dates are valid before proceeding.

Not sure if this may help

In SSMS, R-click the SQL Server node, bring up properties, and select the security tab. You should see options to control login auditing, which is...