Communication Problem between SQL and IIS
-
Greetings all.
Has anyone had any problems which speed between an IIS and SQL box?
My client swears the application is slow. Their reason is because SQL and IIS are on different boxes.
Unfortunatly, I cannot get to the machines as they are in the UK.
They say the two machines are sitting on a 100MBs network, full duplex.
I have yet to have a problem with this but they swear it's the cause of the slow speed.
Anybody know of anything that might cause it. I know there could be thousands of reason....
Maybe I'll use it as an excuse for them to send me there
In small tests I wrote for them, it returns the data fast enough.
Thanks,
Crispin
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
-
How are they reaching the IIS box? Their netowkr may be slow outside of the two together and thus the client has a wrong perception. Use trace options to generate a file to the box with traces around duration and queries. They may be throwing crap at the server with too broad of a definition. And then I suggest test for ID10T errors. Users have the worst habit of pressing submit if they do not get instant transfer which can cause all kinds of issues especially with heavy reports since each query is still going in many cases. We have rigged our pages to remove all the buttons and replace with a PLEASE WAIT WHILE YOUR DATA IS RETRIEVED, YOU WILL RECEIEVE AN ERROR MESSAGE IF PROCESSING FAILS, DO NOT LEAVE THIS PAGE OR YOU MAY FURTHER HINDER DATA RETREIVAL or some other message to keep them occupied and away from buttons.
Personally I am betting on ID10T error or FAILURE AT KEYBOARD problem and user is just too impatient. Make them give you exact details of how they surmised their intuitive troubleshooting. That in itself may be the problem.
-
ERROR AT KEYBOARD, I like that.
In all honesty, I do belive that it's a user error. PEBCAK (Problem exists Between Chair And Keyboard) error.
The problem is they want to know why it's slow but I cannot get to the servers to see/find problems.
The servers are on a 100MBs network, going through to the clients on a 10MBs network.
If there really is a problem, I would first check the NIC. Ever seen what a faulty NIC can do to a network?
I was wondering if anyone might have any ideas. Without being there it's difficult....
Cheers,
Crispin
BTW: Antares686, UDF's do seem to be better in certain places. I'll write a article about them Where they were dog slow and were they were fast. CP
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
-
In situations like this I put diagnostic code in my ASP pages on IIS to tell me how long each piece of code takes (db access,html writes etc). This normally leads me to two things, first that the sql or proc takes longer than it used too (volume of data, no or poor indexes etc) or that the db retrieval is ok but the page build is slow (I have found pages with lots of Response.Write taking a long time).
If you thin SQL is OK, it might be worth checking the IIS server. Is it heavily loaded at the time of slow response? Is there another app that is consuming excessive resources (I have seen these make slick apps run at snail pace).
Doubt if this helps but it works for me.
Far away is close at hand in the images of elsewhere.
Anon.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply