VIM_VCDB transaction log growing hudge

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Database Design » Virtualization » VIM_VCDB transaction log growing hudge

VIM_VCDB transaction log growing hudge

Rate Topic

Display Mode

Topic Options

Author

Message

Frédéric JOFES

Posted Thursday, July 01, 2010 7:10 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, July 01, 2010 8:11 AM
Points: 2, Visits: 5

We have a VCC server witch just updated from 3.5 to 4. Before that VCC database became larger than 4Go so we installed Entreprise edition instead of Express edition.
The recovery mode of database is SIMPLE and Log file of this database take maximum size allowed (500 Mo at beginning, 4 Go after)
A perfstat(logspace) give 99% of free space on log file so we reduce it with a shrink operation.
Log file grow from 1Mo to 4Go in less than 1 hour so, at the moment, we make a shrinkfile every 30 minutes to reduce logfile.
Is somebody have a idea of wath the problem, I will be very happy ! Wink

frederic.jofes@fr.ibm.com

Post #946154

GilaMonster

Posted Thursday, July 01, 2010 7:19 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:54 AM
Points: 37,692, Visits: 29,951

What version of SQL?

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #946161

Stefan Krzywicki

Posted Thursday, July 01, 2010 7:20 AM

SSCrazy

Group: General Forum Members
Last Login: Yesterday @ 4:47 PM
Points: 2,422, Visits: 6,025

If the logfile keeps growing that fast, you must have a lot of activity on the database. If it is growing to that size, it needs the space, you shouldn't be shrinking it. You're slowing down your database because it needs to keep growing the logfile. If your concern is that it is taking up too much diskspace, set the maximum size of the logfile to something that better fits your existing space and then look seriously at buying new, larger hard drives.
If you can, put your log file on a different drive from your database.

--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams

Post #946162

Frédéric JOFES

Posted Thursday, July 01, 2010 8:12 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, July 01, 2010 8:11 AM
Points: 2, Visits: 5

Version : SQL Server 2005 SP2

Post #946196

GilaMonster

Posted Thursday, July 01, 2010 8:18 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:54 AM
Points: 37,692, Visits: 29,951

Check the value of log_reuse_wait_desc in sys.databases. What values (other than NOTHING) do you see for that DB?

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #946201

« Prev Topic | Next Topic »

Permissions