And nothing in the windows system or application log?

Is there anything in the agent error log or windows system log? You may want to even check the SQL Server error log

In 2005 management studio there was a bug where monitor could do some really 'interesting' stuff (in our case it would invalidate the subscription) what you are seeing might be...

If you search SQL 2005 dbcc memusage (an old dbcc function) you can find some functions that will give you an idea if your table is in cache. They...

It's not the backup that is the issue as much as it is the restore (it has to grab all that space)

If anything I might be more worried about I/O overhead if you try to put the trace file on your data or tempdb drive (depending on your I/O system) than...

Also keep in mind SQL Server will use temp tables without you ever explicitly knowing about it.

It would depend a bit if it is 2005 or 2008 but I will recommend...

SQL Server 2008 Query Performance Tuning Distilled -- Fritchey

SQL Server 2008 Internals -- Delaney et al.

An...

The bigger question (that will have more of an impact on you I suspect) is what is the collation on the fields, they should still be what the database was...

Also another big 'if' on this is how much latency you can live with, can you wait 5 seconds for something changed on the writer db to make it to...

The best way to find potential performance differences between queries is to look at the estimated and actual plans using management studio.

Yeah,

Forget what I said, when the snapshot is being created take a look at how much free space there is on the device where the snapshot is going. ...

Yes I have, it is fairly easy on non-clustered servers.

try running SQL Profiler with the error message options turned on, it is likely trying to insert and existing record or something like that.

Well, I would suggest learning to write stored procs from one of the useful resources out there and/or hiring a consultant.

I would offer one free piece of advice however, this...