Can I fix this?

[Funnyhat]

Microsoft OLE DB Provider for SQL Server error '80040e14'

The log file for database 'xosite' is full. Back up the transaction log for the database to free up some log space.

/forum/active_users.inc, line 184


I looked in the Enterprise manager and found nothing... Any ideas would be great.

[jon]

You can either shrink your database(ask support to do this) or increase the amount of space allocated for the database in the control panel.

Jon

[Funnyhat]

Last time I checked the DB was only 4mb in size... This is more than just a log problem?

[admin]

Your logs are 25 MB for some reason I am still working on it for you to fully fix it.. Do you really need the logs?? I know you want the data I have already backed that up my self to make sure I have a good copy of that for you as I am working on it.

[admin]

You should be good to go now.

[electricfox]

Admin, do we need the logs? I would just as soon remove them off my databases - I never use them or even know how. I just thought it was a requirement for the MS-SQL server.

[vonbrocklin]

I'm pretty sure you cannot run SQL without transaction logging. You can set the percentage of db to log file ratio in the CP, and in THEORY, the logs should never grow beyond that percentage and never get any bigger. But it sounds like at least some of them are growing when they should not be...

[Brangwyn]

MS SQL Can not run without the logs, what you should always do however is Raise a support ticket and ask vortech to set your database Recovery Model to "Simple" this will keep the average databae log file size down under 5Mb, you can then allocate much more space to the datafiles (using the little Log/Data percentage thingy in H-Sphere). Also ask for your database to be set to "autoshrink" in that same ticket.

and in THEORY, the logs should never grow beyond that percentage and never get any bigger.

Actually no. MS SQL will still try and write to the logs, what it will cause is the Log full error to occur when MS SQL wants to expand the logs