SQL SERVER 2005 TIMEOUT FRUSTRATION!!!!!!
It would also help if you could provided DDL for any tables used in your queries and details of current indexes on the tables unsed in your queries.Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
July 3rd, 2011 1:07am

I have been battling this issue for quite some time now and no matter what i do, no matter what online resource i use i cannot seem to get any resolution on this. I have a few stored procs. that fall in excess of 10 mins (some 15, some 12 and so on) and every time i try to execute these on our front-end application they result in a timeout. I execute them in ssrs and they result in a timeout, timeout timeout!!! I'm so sick of seeing a timeout from this application i want to throw it against the wall. I understand that optimization can be made within the code itself and there are always ways to improve the sql we write however for large loops that require function looping which cannot be written within main selects, in effect causing double the looping, will always result (especially running over thousands or rows) in slower performance. I have managed to get some of these times down but certain ones fall over the 10 min mark. So far, i've increased the execution time in the .rdl, the timeout settings on the ssrs server itself, our main server, the config file, pretty much every single thing i can think of (including the front-end timeout settings in the connection) but to no avail! Almost all of the links online where people have a similar problem result in a dead-end; giving suggestions, the recipients, like myself, stating they do not work, then end thread! Please help!!!
Free Windows Admin Tool Kit Click here and download it now
July 3rd, 2011 5:37am

Hi SeanTheKing, Thank you for submitting your question here. I can understand your mood now, according to your description, based on my past experiences, in my opinion, the root cause of this issue is the T-SQL queries of the stored procedures, more accurately, the loops is the culprit. In this condition, if it is convenient to you, could you please post the structure of the loops here, may be it can help us to find the improvements for it. Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.
July 3rd, 2011 6:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics