Borja_Mari
Virtuoso
Virtuoso

Hello,

i will try my best to help you Smiley Wink

1) IMHO, the transaction log of your vcenter db has not a "normal" behavior. Using the simple recovery model, the transaction log should be so small!

I have checked sql server expression databases (in simple recovery model) of some vcenters that I'm administering (some bigger than yours), and its transaction logs are smaller than 1 GB, and not really grows over time.

if you are really in the recover model, if the transaction log size increases so quickly, maybe is produced by a long running transaction.

The sql server do log truncation automatically. If the log truncation is delayed (maybe long running transaction?), the reason can be discovered.

2) You can also using manually created jobs (as i commented before in this discussion), to try to shrink periodically the transaction log.

3) IMHO, the only reason to have the transaction log increasing so fast in recovery mode, should be long running transactions. Anyway, I'm not sure that in your small environment, it's a normal behavior seeing this long running transactions ...

4) The sql server agent isn't included with the sql server express edition, then things like db jobs, just can be done manually as i commented before.

Basically, the only way/tool to administer/manage a sql server express version, is using the sql management studio express tool.

Best regards,

Pablo

P.D:

Here you can check some (good?) explanation about the recovery modes in sql server.

------------------------------------------------------------------------------------------------- PLEASE CONSIDER AWARDING any HELPFUL or CORRECT reply. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA . ¡¡Muchas gracias!! VCP3, VCP4, VCP5-DCV (VCP550), vExpert 2010, 2014 BLOG: http://communities.vmware.com/blogs/VirtuallyAnITNoob
Reply
0 Kudos