Hi All.
From last 4-5 days we are seeing log backup file sizes increased from 500 MB's to 100GB files.
What does it indicate and what should we checking at? the queries which are running during those times? This is not just happening during weekends (index rebuilds ..) but during weekdays also its the same behavior.
We take log backups every 30 mins.
Regards,
Sam
June 12, 2024 at 11:48 am
Talk with your db's consumers if they changed usage / implement new stuff / have faulty processes recently / ...
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Is someone doing any form of Index Maintenance? It may not be in a separate job somewhere.... it may be something that someone has added to a stored procedure because they thought it might be a good idea.
Another thing is that someone may have added an index that splits like crazy during inserts and updates.
The easy way to find it would be to go over to Brent Ozar's site and find the article that Erik Darling wrote about how to use Extended Events to monitor for log file growth. It will, of course, require you to shrink the log file a bit but I've implemented it at work and it does fine.
I don't have the link handy but, from the info I provided above, it shouldn't be difficult for you to find.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply