I'd contact Quest on this.

A couple things. First, you don't want to do this in a trigger. You're asking for issues. Instead use the trigger to drop a row in a table (email, new...

You could use my method, which requires some goodwill.

Run Profiler for a few weeks, get a distinct list of procs being run. Now go through the other procs, note which...

It's a rights issue. When you submit a backup comment, it's not your account running the backup, it's the SQL Server service. That service needs rights to that folder.

It is as long as your DR system supports that as well. If not, I'd split only as needed for DR.

Performance wise, no reason a 1TB or a 10TB file...

What's your idea of "healthy"?

I see that used, but it could mean many things. A short list of stuff I'd do first.

1. Make sure backups are being run.

2. Make sure...

Or if you want multiple ones.

Be sure that you use () to block out your ORs and ANDs. AND would match nothing since (I assume) you can't have a single...

You don't see a subquery.

use [database]

UPDATE Table1

SET ProblemType = 12

WHERE problemType = 32

The way you had it written, you were updating all rows.

Should be able to type it in there, or use the search feature.

They add just like AD users as logins.

The way to stop deadlocks is to trace them down and then fix the code so it doesn't allow deadlocks.

Can I ask why the first column is a problem? Perhaps we have another way to do this.

Honestly any other way than dealing with this in the client is asking...

I'd use a batch file, and put the file names in there. You need to control ordering at times, so I'd be wary of a script like the one above.

http://www.sqlservercentral.com/articles/System+Development+Life+Cycle/vcspart3/525/

First, this isn't really a backup question. Please post in the correct forum (moved to admin).

Second, dbcc checkdb is a good place, but what do you mean by health check...

sleeping connections are still connected.

No one should show that db name in sp_who2. If they do, you need to remove them. That includes you connected with SSMS.

It's a communication issue. Can you give the names you used and are you sure the service is running on the 1st computer?