Analysis of databases?

[Guest_imported]

Why does SQL 2000 constantly perform analysis of databases, even when some of those have not been used or are not currently in use?

Our server is a Proliant 8000 with 8 Pentium 550 Mghz processors, 4GB of RAM. Dispite this monster machine, and the fact that we only have 2-3 developers working on it at a time, it is slow as a dog. Response times are horrible, and it times out occasionally. Could this analysis of databases be a cause? If so, is there something we can do?

 

[tlbroadbent]

We've not experienced any general slowdown like you described except that Entreprise Manager seems to start slowly.

What "constant analysis" by SQL Server occurs that raises concerns? What activities are slow - queries, jobs, connections? Have you analyzed current usage, possible locking, cache hit percent, processor utilization, disk activity, etc. to determine the cause of the slowdown? Terry

http://members.home.net/tlbroadbent/sqlarticles.htm

"I'm not dumb. I just have a command of thoroughly useless information." - Calvin, of Calvin and Hobbes

 

[Guest_imported]

Within EManager, SQL Server Logs (Current), I see a great deal of messages simimilair to this:

[date/time], spid51[source], starting up database [dbase name]

(following line):
[date/time], spid51[source], Analysis of database [dbase name] is 100%

These messages repeat for many lines, for our user databases, sometimes immediately following eachother.

WhY?

 

[tlbroadbent]

Check to see if autoclose option is set on any of the databases. There is some indication that it may hurt performance. Yo can turn it off with sp_dboption

exec sp_dboption 'dbname','autoclose',false Terry

http://members.home.net/tlbroadbent/sqlarticles.htm

"I'm not dumb. I just have a command of thoroughly useless information." - Calvin, of Calvin and Hobbes