It's funny, I needed exactly this script and found your article. Thanks for taking the time to post it. Can you post what your changes were to fix it?

Whoops, I stand corrected.  SQL Server does create stored procs by default.  But I could only find stored procs for initial population, conflict resolution, insert, select, and update.  I didn't...

When using transactional replication, you have the option of using a custom stored procedure instead of a standard insert at the subscriber.  This stored proc would run instead of the...

I think the implication is that the record being inserted is a duplicate of one already on the subscriber.  Probabaly because the subscriber was updated by something other than the...

I'd try to avoid the subselect if possible.  While they are fine for a quick and dirty query, they are a slower than using joins for the same purpose.  Probably not...

Actually, I am using the UNDO files for standby mode.  I guess I don't fully understand the purpose of the UNDO file in this scenario because of the very large...

I just had a thought.  Maybe the reason the restores are so slow has something to do with the nature of the transaction log being restored.  While the transaction log...

Hmm, so I guess my next question is:

Why would it take almost 40 minutes to roll forward (or back) 15 minutes worth of transactions?  This is really weird stuff.

I read the responses, but it doesn't sound like you read mine.

I've done more reading on this, and it seems the concensus...

It seems like there is a lot of confusion on fillfactor.  Even BOL seems to contradict itself when it comes to fillfactor:

User-specified FILLFACTOR values can be from 1 through...