Surely it's the same for every question.

The answer isn't a secret, the information required to answer the question is out there somewhere. Some of it you will already know, some...

Replication Latency

Log Shipping Latency

When you come up with your full list of things to monitory, any chance you could post it here?

What are the names of the indexes that aren't listed in EM?

If they all start with '_WA', then they are the statistics that SQL Server builds on non indexed columns...

If these 'hypothetical' indexes have a name that starts with _WA, then they are statistics created as a result of having the 'Auto Create Statistics' option set on.

You can get...

RTM actually stands for 'Release To Manufacturing'

Also, before you go down the 'query hint' route, check that your index statistics are up to date, and do an 'UPDATE STATISTICS' if not. There's a good chance that...

select db_name()

Is it the SELECT part of the statement that is taking a long time to run (i.e. the where((XTELELINK IN.....), or is it the actual UPDATEs (i.e. are there so...

The following should get the 3 results you require:-

select id,max(Date) from tablename

group by id

and

select id,max(Date) from tablename

group by id

having max(Date) < '22/02/2003'

and

select id,max(Date) from tablename

group by id

having max(Date)...

Profiler has a 'Log File Auto Grow' event in the 'Database' class.

For this event, the integer data column tells you by how many pages the log file has been...

SQL Server stores a plan for a stored procedure based on the 'SET' options (e.g. CONCAT_NULL_YIELDS_NULL or ANSI_NULLS etc etc) in force at the time of execution.

If your connections have...

A performance counters bug was introduced in SP3. Have a look at the following link:

http://support.microsoft.com/?id=812915

As long as your reporting users don't need up to date information, you don't need to restore the transaction logs every 15 minutes.

We have implemented a solution that backs up...

Thanks Mark,

I'll do that, as it's easy to add the DROP_EXISTING clause to the script it produces.

You've missed out the "if @@ERROR <> 0 GOTO TRAN_ABORT" check after the last insert.