I had a similar issue a while back, and found the easiest way to get round it was to wrap the query up in a stored procedure that I executed...

Backups are very unlikely to be CPU bound.

Are you backing up to the same machine the database is on?

If so, it sounds like you have some serious I/O problems...

The name of a stored procedure has a data type of "sysname", which is 128 characters.

The schemas for the replication metadata all use sysname, so MS have obviously decided to...

Have you got any triggers on Table B?

Any triggers on the table you are updating?

The query plan seems to be looking at a column called LastCallStatus. Do you have a trigger that does something like set the...

Which version of VS2008 are you using?

I'm sure I saw a comparison of the versions somewhere, and not all versions support TSQL debugging.

What profile properties are you changing?

Another thing that I have seen make a big difference is the connection options e.g. ANSI_NULLS. Make sure query analyzer is using the same options as the connection from your...

Have a look at my earlier post about putting the set statements at the beginning of the procedure.

The bizarre solution was courtesy of Microsoft Support

SQL Server creates the pseudo inserted and deleted tables by reading the changes from the transaction log.

Performance is therefore going to be affected by the number of changes it has...

Delete the tables.

Don't forget, the tables are in Tempdb, so they will be removed every time you restart the instance, so you can do no harm by deleting the whole...

Where are you seeing this error?

This table (and a few others) are used to populate the information in Replication Monitor, and don't actually have anything to do with the replication...

Your understanding is partially correct, the only thing that you are missing is:-

You need to set the isolation level on the connection that is reading the data (your website), not...

Microsoft Press have produced a book 'SQL Server 2000 High Availability' (ISBN 0735619204) that explains clustering in huge detail. Search this site or Google, and you will find plenty of links/articles...

Clustering works by having disk storage that is attached to all of the nodes in a cluster. When a nodes running SQL Server fails, one of the other node takes control...