best way to optimize certain tables

I have a SqlServer 2000 running 7 databases. One in particular is slower
than the rest specificaly on certain tables. It seems the problem comes
from the volume of data, but I don't think 3000 lines can be considered a
big table. I have indexes on the principal keys, but it did not help.
thank you
Hi,
Identify the stored procedures , Queries taking more time / CPU. Use the
profiler tuning templace to identify this. After that save the
file as a workload table or file. Use the workload file as the input file
for index tning wizard.
I feel that this slow responce is due to the lack of proper indexes.
You could also use the Execution plans to tune your queries.
Thanks
Hari
SQL Server MVP
"Fernand St-Georges" <fernand.st-georges@.videotron.ca> wrote in message
news:Ethwe.79344$Yu4.927653@.wagner.videotron.net.. .
>I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
>
|||Tables are not slow. They are just data containers.
Queries can be slow, if they are not written properly, or when the
underlying tables are not properly indexed. You could follow Hari's
advice to analyse where and why they are slow.
You could also give the Index Tuning Wizard a try.
HTH,
Gert-Jan
Fernand St-Georges wrote:
> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
|||Check the queries and use index tuning wizard.
Are you re-indexing the tables frequently?
Thanks
Ravi
"Fernand St-Georges" wrote:

> I have a SqlServer 2000 running 7 databases. One in particular is slower
> than the rest specificaly on certain tables. It seems the problem comes
> from the volume of data, but I don't think 3000 lines can be considered a
> big table. I have indexes on the principal keys, but it did not help.
> thank you
>
>