My company is currently in the process of migrating our client-facing web server. This has been an ongoing project for several months(namely because we're making a very, very, big leap in technology) and we are now less than a week away from our migration window closing. We have hit a wall with one of our client-side processes that needs to be fixed before we can go live with the new server. Everything else seems to be working correctly though.
In short, one of our stored procedures keeps timing out. It works fine on our live server(completes in <1 second), however when we try to run the process on the new server, it times out after 30 seconds. Through testing and tracing we have pinned down the exact procedure that is timing out, but have no explanation as to why it works in our production environment and not on our replacement server.
Some possible explanations we have:
Network Latency - Unlikely at this point, but possible because the production server and it's replacement are in two different physical locations with low bandwidth between them.
Something to do with MSDTC - We encountered some errors with this process that...
1>