bharat sethi (12/18/2013)
Hi! Then how do we improve it?
if you are selecting all rows(we still didn't see the query, which might be improved), then you can't speed it up with indexing;
so it comes down to amount of data returned, and the underlying hardware.
do you really need to return 207958 rows of data?
if it's being used to populate a web page, the data may be returned very quickly, but the creation and rendering of all the TD / TR tags takes any browser a TON of time to build a page...you need to identify where they "slowness" is occurring.
can you change it so it provides an intelligent summary of the information, instead of all the data? what are you doing with the data?
do you really need every column in the query? are you returning image/text/varchar(max) fields? are they even being used if they are returned?
is the slowness on the LAN, or over the internet? is your LAN gigibit speed?
--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!