200 records should be displayed quickly unless you have some issues in your stored procedure. Have you checks for locks? Do you have indexes on key columns? Does your main query contain many su-queries or correlated queries?
I have written code to display over 2000 records in less than 10 seconds. A time-out issue usually indicates issues with the database. Dallas Quoting vmace_20850 <[EMAIL PROTECTED]>: > --- 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 Links > > > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Domains - Claim yours for only $14.70 http://us.click.yahoo.com/Z1wmxD/DREIAA/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/
