Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Index followed by stats

Author  Topic 

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2003-10-14 : 15:09:58
Hi,
a.
I would like to know if these jobs should run in an order to see some performance improvement.
1. First run DBREINDEX
2. Then run Update Stats.

b.
I am having performace issues almost every monday and tuesday.
what worries me is that say for example, user complained that the process took more than 1 hr (ideally it should take only 20 mins) to complete so i go back and run index job then user reruns it and sees it took only 40 mins (still not ideal). Next day user runs same process and it takes again 1-2 hrs to run. Yes, there is tremendous data change but should the performance degrade to this level?
I have no control on the process (cobol sql), I cannot change it so all I can do is look at the sql and make changes to indexes on the table but this is happenening now, it was okay for a long time.

I have traced this process and only other jobs that happen are 1-hr log backups during user intervention.
Thanks,
Sarat.


**To be intoxicated is to feel sophisticated, but not be able to say it.**

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-10-14 : 15:38:29
It sounds like you need to run DBCC INDEXDEFRAG a couple of times per day. Does DBCC SHOWCONTIG show a lot of fragmentation?

I am not sure that it would matter which order you ran those jobs in.

What does the server performance look like during these problems? Is CPU maxed out? How about memory?

Tara
Go to Top of Page
   

- Advertisement -