GilaMonster,

You're right!

Its the stats update. That fixed it. However Im trying to understand how this works. Would you be able to give some idea? Thanks.

Im assuming and expecting a value of 0 to be most ideal

yes, I did think so! and then i went on to verify the views that show me the statistics last update.

I then realise that we also have a job...

Hey,

Im back at this again. I rebuilt my index and that fixed it!

However , now after couple of days ( i should say ), the database is exhibiting the same...

thanks

Yes, i was able to view the graph and cost from the studio, but i could not make head or tail out of it!

Yes, they, the vendor have released couple of patches/workarounds to address those issues. Thanks.

Yes' Got the culprit, you're right.

Its the vmware stored procedure. Ah!

Thanks..

Adding on to my earlier message:

Noticed the following process triggered via SQL agent running since then; seems to be a DELETE command:-

purge_stat1_proc

Thanks, That returned me the following results. From the start time this seems like this process's been running for over 3 days.

Oldest active transaction:

SPID (server process...

i've had to restart it again, because its run off space again. i will have an update soon..

unfortunately all i get to see from DBCC OPENTRAN is:

No active open transactions.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

yup, a lock has been placed on the database by a process with the following atrributes:

owner id = 0

owner type = shared_transaction_workspace

objectid=0

request mode = S

I notice one idle session that have open tranasaction.

The program name is Service Runner and i suspect its probably a VMWare system process with status as sleeping and lock_timeout...

dbcc opentrans tells me No active open transactions.

whereas the following query returns two rows

login name session_count

Adminstrator 3

sa ...