If the indexing fixes it, maybe have the dba
setup a maintenance task to rebuild the index on the table in question once in
a reasonable period.
-----Original Message-----
From: vmace_20850
[mailto:[EMAIL PROTECTED]
Sent: Thursday, July 29, 2004
11:39 AM
To:
[EMAIL PROTECTED]
Subject: [AspNetMetroArea] Re: Time Out
Expired
--- In [EMAIL PROTECTED],
"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
Hi there,
You might have found a solution to your problem
since your post, but
in case you have not, I would suggest the
following: have the sproc
return 10-20 recs at the time( paginate on the
server).If you really
must display 200 recs, increase teh timeout
property and run a
profiler , as someone mentioned in here.
Vlad
| Yahoo! Groups Sponsor |
ADVERTISEMENT
![click here]() | |
![]() |
Yahoo! Groups Links