You didn't mention what database you are using. I
assume you're using SQL Server.
There is a property called CommandTimeout in
SqlCommand. The default setting is 30 seconds. You
can change that to whatever makes sense to you.
I don't know how complicated your stored proc is.
Unless you're joining dozens of tables, taking more
than 30 seconds to return 200 records seems too long
for me. Sometimes, indexes on single column is not
efficient for your query. Depending on your where
clause, you may need to add compound index to speed it
up.
Thanks,
Mickey
--- tegestmelu <[EMAIL PROTECTED]> wrote:
>
> I get the following error when trying to run a
> stored procedure from
> Vb.Net which selects about 200 records.
>
> The error says:"Time out expired: The time out
> period elapsed prior
> to completetion of the operation or the server is
> not responding"
>
> When our Db rebuilds the index of the table which
> the stored
> procedure uses the problem seems to go away for some
> time.
>
> I would appreciate it if anybody has any suggestion
> how to fix this
> problem.
>
> Thanks
> Tegest
>
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/X1EolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetMetroArea/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
