--- In [EMAIL PROTECTED], Mickey Yang <[EMAIL PROTECTED]> wrote: > 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.
I agree, typically only data warehousing activities or other backroom data-intensive operations should take that long. If this is connected to a website, that's WAY too long of a query--nearly all people will click Stop or Back if they have to wait that long. There is probably some inefficient SQL code that could be cleaned up or index config tweaks to make it much faster. You might try running SQL Profiler to see if it gives you any info to help you troubleshoot it. Post the SQL sproc code to the list below, you'll get better, quicker help there... http://groups.yahoo.com/group/ASPNET_SQLSERVER/ ------------------------ 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/
