SQL Translogs are very large and aren't shrinking in size.

I do full backups of my database twice a day.  And I back up the transaction logs every 30 min.  Before last week the transaction log backups were between 1 and 10 MB depending on the number of transactions performed during the log backups.  However, last week the size grew to 500 MB and stays there even if very few transaction are performed between log backups.  I have tried shrinking and truncating the log file.  But it just jumps straight back up to 500MB.
LVL 1
vbchewieAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lcohanDatabase AnalystCommented:
What is the Recovery model of your DB(s)? Full, Simple, Bulk Logged?


"But it just jumps straight back up to 500MB" - there must be something filling that T-log as they don't grow for nothing. Can you open SSMS and check the standard "Disk Usage" report? this will show you at least when and by how much your DB files Autogrew
0
vbchewieAuthor Commented:
Full,

It looks like its currently using much less space than it has allocated.
I looked at the disk usage and in all 3 cases after the first log back up grew to the size of 4GB in the first hour and then stays there. but I still don't understand why the log backups are stuck a 500MB.  We are not a 24/7 shop database transaction drop off significantly after 6pm.  Yet the log backups stay at 500MB throughout the night.
SQL-Log.png
0
SJCFL-AdminCommented:
I do not see any allocations on that report. usually if space isallocated, it shows on the report.  Are you sure that the shrink ever sucessfully reduced the size?  I believe this is what lcohan was leading to.  that if it had been shrunk, you would see evidence of it on the report.  when i get a stubborn log file that does not want to shrink because of high activity, I sometimes have better luck trying t-sql commands than the gui interface.

To do that, when you get to the point on the gui to do the shring, click on click on generate script  instead.  Then cancel out of the gui and it will leave you on a panel with the shrink command.  (So i am lazy. yes i could have typed it ...)

If I have transaction log backup jobs (and I always do), kick them off. then as soon as they finish, I run the script.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

SJCFL-AdminCommented:
And this is assuming that you did check to make sure that the allocations on the files properties page had not been tampered with and increased to cause the larger size. Someone could have changed the log size allocation increase thinking it was the data by mistake...
0
vbchewieAuthor Commented:
Sorry I crop it.  Here is a new pick.  Okay so I check the initial size and it is 4GB so that explains why the logfile increases in size.  As you can see from the picture the transaction log usage is growing fast.  I checked the Batch Requests / Sec and it is hanging out around 6000 and 8000.  I think it usually around more like 800 to 1000.  How do I find out where this massive amount of request are coming from.Data Usage Auto Growth
0
SJCFL-AdminCommented:
Check to see if you have a maintenance jobs running at that time.  i have seen this happen when somone includes index rebuilds or reorgs and does not allow for transaction log backups in between.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.