MIS Systems Thread, massive sim.ldf file - anyone else had there's suddenly grow? in Technical; logged a call with our SIMS team as the log file has reached almost 60GB which is plain daft.
The ...
-
7th December 2011, 04:08 PM #1 massive sim.ldf file - anyone else had there's suddenly grow?
logged a call with our SIMS team as the log file has reached almost 60GB which is plain daft.
The SIMS team setup the server ages ago but they havent installed any of the SQL management suite to actually look and what logging options have been set?
Not that happy with installing the suite just in case they grumble about it being unsupported.
I know they have recently pulled the autumn upgrade and wondering if this might be a reason for this.
-
-
IDG Tech News
-
7th December 2011, 04:13 PM #2 It's quite likely that your backups are not truncating the log file.
What's your backup mechanism?
-
-
7th December 2011, 04:24 PM #3 Have you tried the ShrinkLDF utility?
-
-
7th December 2011, 04:34 PM #4
- Rep Power
- 14
It's quite likely that your backups are not truncating the log file.
I second this, we have had this before there is a setting that can be change but can not remember it.
-
-
7th December 2011, 04:59 PM #5 Before attempting to shrink the file (in itself it's not going to cause too much of a problem, apart from being very big) it's best to try and find out why it's been growing, or we'll end up with the same problem again.
We need to know the database model (simple/full) and the backup mechanism used.
-
-
7th December 2011, 07:03 PM #6 You can install the SQL Management tools on another box and connect to the database server to figure out what's going on (assuming the DB server accepts remote connections).
-
-
8th December 2011, 08:18 AM #7 after speaking with the SIMS team they ran a script to change the logging/backup method to simple as it was set to full.
further investigation suggests that the backup also had a problem and wasnt completing properly and not truncating the logs..
-
-
8th December 2011, 09:18 AM #8 Good job you spotted the problem.
-
-
8th December 2011, 09:30 AM #9 
Originally Posted by
SHimmer45
after speaking with the SIMS team they ran a script to change the logging/backup method to simple as it was set to full.
further investigation suggests that the backup also had a problem and wasnt completing properly and not truncating the logs..
We've suffered from the "recovery model Simple/Full issue" bloating LDFs in the past. Having set it to Simple manually a few times (SQL Server Management Studio > Database Properties > Options > Recovery Model) I tend to check it after each SIMS release because several have kindly set it back to Full again!
-
-
9th December 2011, 08:57 AM #10 So how big is the database now?
You can also change the autogrowth properties to slow it down. We have it set to 10mb auto growth here.
Sims mdf is 2gb
the ldf db is 10gb
Is there any document saying what a good ratio should be?
Last edited by zag; 9th December 2011 at 09:07 AM.
-
-
9th December 2011, 09:06 AM #11 
Originally Posted by
zag
So how big is the database now?
You can also change the autogrowth properties to slow it down. We have it set to 10mb auto growth here.
Sims db is 2gb, the log db is 10gb
10gb is huge still... Ours ldf is 1.1Mb at the moment, and it'll grow over the day to probably 10Mb or so, then the backup will truncate it back down to about 1Mb again.
-
-
9th December 2011, 09:18 AM #12 currently the LDF stands @ 1.5MB.
the SIMS team have a script to set the properties if SQL studio isnt installed.
-
-
9th December 2011, 09:35 AM #13 Avoid using auto-growth as a management tool.
Always size the databases correctly, an auto-grow will halt the database engine while the server extends the files.
Switch on auto-grow by all means, but set it so that the increment is a large size (rather than a percentage). This means that if the server ever needs it (for whatever reason), it will extend the files by a large, defined increment, rather than nudging the file size every so often.
Forget auto-shrink, do this manually if you must.
Here's why.
http://blogs.msdn.com/b/sqlserversto...hrink-off.aspx
Last edited by jinnantonnixx; 9th December 2011 at 09:39 AM.
-
-
9th December 2011, 09:42 AM #14 I just reduced to 10mb by using Shrink >> file >> log
99% was free apparently!
Set a limit of 1gb now.
Last edited by zag; 9th December 2011 at 09:51 AM.
-
-
9th December 2011, 10:39 AM #15 Anyone using backupexec 2010? What settings for the SQL agent are you using to truncate the logs?
-
SHARE: 
Similar Threads
-
By daz666 in forum General Chat
Replies: 7
Last Post: 8th April 2011, 06:35 PM
-
By Dos_Box in forum General Chat
Replies: 25
Last Post: 8th October 2010, 08:35 PM
-
By DaveP in forum Jokes/Interweb Things
Replies: 5
Last Post: 28th June 2010, 08:41 AM
-
By Jake in forum MIS Systems
Replies: 3
Last Post: 9th September 2008, 06:23 PM
-
By edie209 in forum MIS Systems
Replies: 11
Last Post: 22nd November 2007, 10:30 PM
Thread Information
Users Browsing this Thread
There are currently 2 users browsing this thread. (1 members and 1 guests)
- sturgeo
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules