Reply to Message

View discussion in a popup

Replying to:
the_xploit
Contributor
Contributor

Thx alot for your help! To sum this thread up:

My Settings / Setup:

- Settings should be fine (ty for your stats MGlasson)

- i now also checked statistics but with my 2 physical hosts and my not even 20 machines it gives me 0.47GB DB size... => no problem because i can grow to 10GB (ty for your hint with statistics MGlasson)

Solutions so far:

- manually created jobs that shrinks DB / Files (ty Pablo)

What could still help further?

1) It is still unclear why the T-Log grows so fast!? (Today i cloned another machnie with absolutly zero effect on T-Log) some information to this point:

     - the DB (VIM_VCDB) seems not to be the problem after changing the retention policy and other settings... It seems that only the T-Log gets full from time to time...

     - the T-Log is now 9.9GB but my vCenter is still running! When i shrink DB now it will take like 5Min and T-Log is empty

2) are there any scripts that do that schrinking? (And why they are not built-in if this is the only workaround!?)

3) are there any other solutions on preventing T-Log from getting filled (rsp. help getting smaler again..other than shrinking)?

MGlasson wrote:

also do you have sql server agent running on the server, and do you have the pictured below jobs set to run

36036_36036.pngpastedImage_4.png

excuse my delay getting back to you.

4) What is it about that SQL Server agent? Never heard of that! Where should i find that agent? And where is your screenshot coming from? SQL Mgmt Studio?

Reply
0 Kudos