Need help sizing a SQL 2005 T Log drive in a cluster

[vwman]

ARRRRRRRRG!!! <!--[if gte vml 1]>

<![endif]-->!http://communities.vmware.com/images/emoticons/angry.gif!

Am running VC in a SQL 2005 cluster and have apparently severely undersized

the Log drive (8GB). So VC is constantly crashing because my log drive is

filling up.

How large can I expect the T logs to get? I am running an 8 node ESX

cluster with about 150 guests but am planning on adding another 8 nodes this

fall.

I never had any of these problems when I was running SQL Express, but since

the upgrade last week.....

I am also getting alot of these errors in the event log. I believe

that they are related to the T Logs filling up.

The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter

Server ) cannot be found. The local computer may not have the necessary

registry information or message DLL files to display messages from a remote

computer. You may be able to use the /AUXSOURCE= flag to retrieve this

description; see Help and Support for details. The following information is

part of the event: Failed to intialize VMware VirtualCenter. Shutting

down....

Thanks

vwman

[kjb007]

Your drive size is big enough. You need to make sure to setup some database maintenance jobs to backup and truncate your transaction logs on a nightly basis. Without this, your logs will keep growing. Also, what is your recovery point objective here? If you don't need to restore up to the minute of a db failure, then check to see if you are running in simple recovery mode. Simple recovery will let you restore up to the last full backup, while full recovery mode, will let you recover using full backup and the transaction logs. If you don't need that restore capability, use simple recovery mode. You can also run a full backup now. Then truncate your transaction logs and zero them out. Then, the full backup will be including all current data, and truncate will zero out the transaction logs.

-KjB

[williamarrata]

vmman,

Tyr looking into this web site and see if it helps you in your situation.

Hope that helped.

[vwman]

Finally ended up wiping the db and starting over fresh. Spoke with support and they said that there can be issues upgrade from SQL Express and that it is probably best to start over fresh.