You should either doit from client side code (the loop) or distribute your scripts to the master ( using sp_* ) and running then your stuff locally by looping through...

http://www.simple-talk.com/prettifier/

Both. At restore time you won't be able to execute if there are connections to the DB.

Blocking is a "normal" thing to happen on a very concurrent database as long as it does not goes out of control and starts giving you timeouts!

On the other hand...

Apparently someone is UPDATING STATISTICS on your database

If you can quiesce *all* replication agents.

Backup and Restore WITH MOVE can be used!

It is an outage, period. If you can't do your job it must be counted as an outage.

Where I work people (including me) are crazy about all sorts of "metrics"....

I recommended DatabaseID because most event support it. Database Name on the other hand is not supported by many event types. It is not difficult to tell which database is...

Nice one

Have a look as INFORMATION_SCHEMA.COLUMNS

totally agree.

The Problem is that [A-Z] != [ABCDEFGHIJKLMNOPQRSTUVWXYZ] When COLLATE is used

[A-Z] apparently means: AaÁáÀàÄäBbCcÇç ... wWxX... When COLLATE is used.

NOTE: I can't back this up with any...

select year(SuggestionDate) as YearOfSuggestion, count(*) as Total

from suggestions

group by year(SuggestionDate)

order by year(SuggestionDate)

>>> It was full of errors. <<<

Which Errors ?

Start by using the Performance Tuning Trace template, include DatabaseId filtering by Number of Reads and Duration.