When you dropped and added the article back to the publication did you reapply the sp_MS stored procedures for that article? Maybe you could script out the procedures using sp_scriptpublicationcustomprocs...

What else is running on the subscriber at the time the delays occur? If there's no blocking your disks or CPU might just be busy and take longer to apply...

Changes to subscribers are made in the same order that they are first applied at the publisher.

It sounds like you might have blocking. Next time you catch it happening I'd run a sp_who2 and see if you can observe a block in progress. Do you have...

Horizontal filters (row level filtering) are applied to an article at the publication level; you cannot apply a horizontal filter on a subscriber-by-subscriber basis.

You have two options:

1) Set up...

Based on what you said I assume you're only talking about publications where your server that you're migrating is the publisher, not where it's the subscriber. If you can ensure...

Using your logic I could also suggest that the tools necessary to configure IIS shouldn't be installed on a server. After all IIS can accept connections from another machine and...

I doubt that whomever is trying to get into the server is doing so to be able to run the management tools. Besides, most SQL Servers I know accept external...

BGINFO is a handy tool but I don't think it lists the number of sockets in a machine - only the number of cores.

SYDI Server does exactly what you're looking...

I disagree that servers don't need management tools on them (I do agree they don't need BOL). I put the management tools on my production servers sitting in colo facilities...

Update: Whatever the issue was, a reboot cleared it. Go figure.

Good thought on the memory...OpenManage doesn't show any hardware level errors and there is nothing in either the Windows Event Log or the SQL Error Logs.

FWIW here's the statement:

DECLARE @qWordItems1...

Use SYDI-Server to get this plus a lot more information about your server that you would probably find useful.

See http://kendalvandyke.blogspot.com/2008/06/network-documentation-with-sql-2005-and.html for more details

That makes it pretty easy then. FWIW if you have the new server ready to go you've got a great opportunity to restore backups from your current production box and...

Is there any kind of replication or log shipping\mirroring happening on your current production box?