Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Log File Continues to grow


Log File Continues to grow

Author
Message
Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36316 Visits: 18752
you say mirroring was turned off or disabled, but that doesn't mean it was done correctly. If it's not removed from the source, and you don't have a destination, the log will continue to grow.

When you query sys.databases, what is returned for the log_reuse_wait_desc? It should be a number.

If this is 0, then either you have an open transaction, or you are not running log backups as you think you are. Double check everything is correctly configured.

you could try switching to simple mode, then back to full, then take a full backup and shrink the log (DBCC SHRINKFILE). then monitor to see what happens.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
krypto69
krypto69
SSC Eights!
SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)

Group: General Forum Members
Points: 871 Visits: 2420
you say mirroring was turned off or disabled, but that doesn't mean it was done correctly. If it's not removed from the source, and you don't have a destination, the log will continue to grow.

When you query sys.databases, what is returned for the log_reuse_wait_desc? It should be a number.

If this is 0, then either you have an open transaction, or you are not running log backups as you think you are. Double check everything is correctly configured.

you could try switching to simple mode, then back to full, then take a full backup and shrink the log (DBCC SHRINKFILE). then monitor to see what happens.


I know that I disabled mirroring about two years ago. I know that both the source and destination do not show mirroring enabled. But, is there another way to verify?

When I run the query :

select log_reuse_wait_desc from sys.databases where name = 'Ultipro_WSI'



Results do not include a number just: LOG_BACKUP

I'll try switching from simple to full right now and then shrink.



krypto69
krypto69
SSC Eights!
SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)SSC Eights! (871 reputation)

Group: General Forum Members
Points: 871 Visits: 2420
..just a follow up..

I was able to shrink the log successfully.



ronang
ronang
Grasshopper
Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)

Group: General Forum Members
Points: 22 Visits: 136
Hi

I had a similiar issue with an OLTP db on one of my servers, all the symptoms look to be the same. My suggestion is to investigate if the transactions within your log file are being committed or hardened to your data file. The problem I found was that across tran log backups the uncommitted transactions were remaining. The resolution was then to weekly run independantly a TRUNCATE LOG SQL Agent Job, ensuring that uncomitted transactions were rolled back.

Regards,
Ronan
Divine Flame
Divine Flame
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1573 Visits: 2801
ronang (6/18/2013)
Hi

I had a similiar issue with an OLTP db on one of my servers, all the symptoms look to be the same. My suggestion is to investigate if the transactions within your log file are being committed or hardened to your data file. The problem I found was that across tran log backups the uncommitted transactions were remaining. The resolution was then to weekly run independantly a TRUNCATE LOG SQL Agent Job, ensuring that uncomitted transactions were rolled back.

Regards,
Ronan


Manually truncating the log weekly should not really be required. You can always check for the uncommited transactions using DBCC OPENTRAN command.


Sujeet Singh
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search