Thanks. This helped me get to a solution for now.
In my SP I have four parameters, the third one is @policy_no_passed.
When running in production this will be NULL and return all policies.
When running ad-hoc for troubleshooting I can populate it with a specific policy number, and it takes only 15 seconds to run.
I changed the SQL Command text from just exec my_proc... to this:
SET NOCOUNT ON SET FMTONLY OFF exec my_proc par1, 'par2, 'a policy number', 0
I'll change the third parameter back to NULL before saving. Hopefully I won't run into these timeout errors.
Main Topics
Browse All Topics





by: dodge20Posted on 2009-09-28 at 13:44:36ID: 25443204
Doesn't look like there is anything you can change.
nso/archiv e/2007/12/ 14/query- t imeout-exp ired-when- trying-to- preview-th e-data-fro m-the-ole- db-source- editor-in- bids.aspx
http://blogs.msdn.com/ialo