You are viewing limited content. For full access, please sign in.

Question

Question

Workflow database log with large size

asked on July 2, 2015

I am currently working with a customer that has Workflow log files that exceed 200Gb in size. This would be the .ldf file. The .ldf file should not be that great in size. Is there anything that clears this up or compresses it?

0 0

Answer

SELECTED ANSWER
replied on July 3, 2015

See SQL Transaction Log is taking up all drive space?  Most likely, either the backup mode for the DB is not set to simple or they are not backing up the DB at all.

1 0
replied on July 6, 2015

The database was set to full instead of simple. I changed it to simple and shrunk the DB.

0 0
replied on July 7, 2015

As long as you are aware that simple gets rid of any possibility for point in time restores, then this will work just fine.

0 0

Replies

replied on July 2, 2015

It sounds like your transaction log backup is not running properly as that is what empties out the LDF file. This keeps it so you can do point in time restores but will also keep expanding until you get a proper backup.

You should be able to check how much transaction log space is in use by right clicking on the database in SQL Management Studio ---> Reports ---> Disk Usage. It will tell you what percentage is being used towards actual transaction logs. If most is unused, you should be able to get away with a shrink which will remove the unused allocated space.https://msdn.microsoft.com/en-us/library/ms189035.aspx#SSMSProcedure

Keep in mind if it is legitimately using it, it will grow right back. 200GB is very large though and there has to be some reason it has gotten so large.

3 0
replied on July 6, 2015 Show version history

So given that the database is set to be allocated to an percentage of space of the disk, if shrunk, it will still expand to the given size if it does grow to that size correct? Also, will this impact performance?

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.