Hi sfeldman,

I never found out what the resolution was because I left the company shortly after this post. At my departure we didn't attempt moving to the tempdb, it wouldn't have been an option because the table being populated is a permanent table.

Maybe it will help if I tell you about where I left off.

When I left, the only work-around I had was to leave the system in simple recovery mode. This didn't close the issue as the product we were supporting had a requirement to support Full recovery model so the attempts at resolution went two paths,

Our issue for our client was that the replication delay was causing an error in our application, “Failed to validate database replication”, while deleting and/or saving a new or modified [product name omitted] Query is caused by two factors:

To address the issue we changed recover to simple (close monitoring) and started two paths

1. A case was opened with Microsoft

2. Our developers (in case MS wouldn't fix it) began to modify the product to not require immediate replication between "Sites" thus eliminating the error condition. Also investigated reducing the number of reads and writes of the offending procedure.

Work was underway (not completed) when I left.

Make sure you have the latest fixes from Microsoft because if MS fixed this it would have been part of their GA hotfixes (the company I worked for would only accept official and supported fixes).