tag:blogger.com,1999:blog-6837250508009744375.post9147324614437333336..comments2023-05-17T19:46:47.920+05:00Comments on Arsalan Tamiz: Query Timeout in ADO.Net but NOT in SQL Server Management StudioArsalan Tamizhttp://www.blogger.com/profile/03883319971948565803noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6837250508009744375.post-58361045724031648702008-12-17T03:57:00.000+05:002008-12-17T03:57:00.000+05:00This issue is not limited to ADO.Net using VB.Net....This issue is not limited to ADO.Net using VB.Net. I had the same thing happening in an all C# app with a C# DAL. However the "WITH RECOMPILE" still fixed it. I'm thinking that it might have had something to do also with the sorting that's available on the page, requiring to many executions of the procedure returning the same result set. So I'll probably cache the results and use the cached results for the sorting...PapaStahlhttps://www.blogger.com/profile/09133056315991878528noreply@blogger.comtag:blogger.com,1999:blog-6837250508009744375.post-64025048109576459662008-08-29T10:13:00.000+06:002008-08-29T10:13:00.000+06:00Yes maybe "Parameter Sniffing" can fix this issue ...Yes maybe "Parameter Sniffing" can fix this issue also, we can try. But the problem is that the procedure never slows down when it is executed from SQL Server Management Studio. The exception is thrown in application (which is obviously thrown by ADO.net)Arsalan Tamizhttps://www.blogger.com/profile/03883319971948565803noreply@blogger.comtag:blogger.com,1999:blog-6837250508009744375.post-19376615593294374762008-08-28T14:52:00.000+06:002008-08-28T14:52:00.000+06:00This problem has to do with "Parameter Sniffing"This problem has to do with "Parameter Sniffing"Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6837250508009744375.post-36747694342875037582008-08-27T13:44:00.000+06:002008-08-27T13:44:00.000+06:00I was having the same problem before.. and it work...I was having the same problem before.. and it works for me as well.. thanks a lot :)Anonymousnoreply@blogger.com