asked on

How to resolve performance issues on SQL 2000

Hi Experts,

I wrote a stored procedure to retrieve lots of data say from around few millions database records. I have use all the optimizations such as use of temp table, indexes etc... though the peformance improved but still we want performance to increase. What are my options?

a) Without Migrating to SQL 2005, can we use the features of 2005 for the speed, i understand this is a silly question but something like writing that proc in 2005 calling from 2000 etc etc...

b) Any other options i have? Without doing any big change.

Any suggestion will be highly appreciated.
Regards,
Rithesh

anandarajpandian

Hi Star,

Can you use Table variable instead of Temp table, and using profiler for checking which code it's taking long time,and try to avoid left and right outer join.

Regards
anand

Neil Russell

First optimization most people overlook is the hardware.

What is the server spec of the machine this is running on?
How many processors? How many cores?
How much memory?
What Raid type? How big? How many disks?

Girard Tabañag, MBA, MIT, MACS CP

I encountered this similar issue and what we did was to use pagination wherein you only retrieve a certain range of data and display a portion of that. Basically, this is similar to Gmail. You will notice that when you do search that matches a lot of emails, it will only retrieve and load up to a certain point and display something like "Page 1 of hundreds".

I hope this will help you too.

vinurajr

what is the current execution time and what is the process u are doing in the SP?

ASKER CERTIFIED SOLUTION

Lowfatspread

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial