The operation timed out
I work on a very long SQL Stored Proc (36,600+ lines) and have never had an issue until today. When I load the proc in Linqpad 6 I now get what seems to be the entire code base, but now it is accompanied by a modal error: The operation timed out. I would like to know if this message is connected to the size of the proc and if I need to be concerned (or it is simply an edge case)?
When I load the Stored Proc in Linqpad 5 I get no such error message.
Thanks!
Jeff
Comments
Try executing the following query on that database with the language to 'SQL':
sp_helptext '<stored proc name>'How long does the query take to execute?
Joe:
Per the bottom of the screen: Query successful (2.574 seconds)
You're running into the limits of what LINQPad can handle with regard to size of the document.
Thanks Joe for taking the time to confirm. As I noted, I get no such errors when running version 5-- assuming this SPROC is not getting any smaller, would you recommend that I continue using V5 as a workaround-- or is that also potentially problematic?
Thanks,
J.
I've adjusted the timeouts in LINQPad 6 to be more in line with LINQPad 5, so you might have more luck with the next build. When the SP grows further in size, however, you might also run into issues in LINQPad 5.
The other issue is that the editor is not designed to work well with 36,000 line documents. It will be sluggish.
BTW: I mostly use SSMS when working with the aforementioned SPROC, but when I work on queries that generate lengthy report output, I revert back to Linqpad as SSMS inherently truncates long output-- requiring extra work to look at the results.
Thanks again, Joe. We made the internal decision to take evasive action and begin breaking up that massive SPROC.