Identify Task Delay on Joined Layer Within Map Service

Discussion created by u0281276 on Feb 9, 2011
Latest reply on Feb 28, 2011 by mflawton
I have a map service that has a layer within it that is joined to an outside (non-sde) SQL Server database. On our development server it works fine. But on one of our production servers when I try to run an IdentifyTask against it I get a 30 second delay. I've had our network guy do a trace on the process and he can see the request from my web app hit our server immediately, but then there is a 30 second delay (exactly the same time consistently) before our server makes the request to the joined SQL server and then returns the data back to my web app. Just wondering if anyone else has run into the same problem.