Hi
You should look at the query execution plan, details about these can be
found in books online and in "Inside SQL Server 2000" by Kalen Delaney ISBN
0-7356-0998-5.
If you have your query in Query Analyser, use CTRL+L to display the
estimated execution plan or CTRL+K to display the used plan. This should
indicate where the query is being costly. It could be that the statistic are
out of date.
You may also want to look at using SQL Profiler to check for blocking and to
view what other activity is being processed. If you run Profiler for a period
of time, you may want to use it as input to the Index Tuning wizard to see
what suggestions it may give.
Overall performance tuning information can be found in the "SQL Server 2000
Performance Tuning Technical Reference Manual" ISBN 0-7356-1270-6
John
[quoted text, click to view] "anand" wrote:
> In the firm which i am working there is no dba as such
> so we are facing a big problem with the performance with sql server
>
> we have a table which contains lacs of records but when retrieving it takes
> too much time
>
> also ther are 4 to 5 indexes on that tables
> again adding a new index is a great task
>
>
> pls help me with this with how it's possible to make it out
>
>