One issue that can re-occur in some environments is a growing transaction log. This can be a major pain point if we don't consider how we'll use our database. In the video, TSQL: Transaction Log Growing Too Big, I quickly discuss some points around the transaction log growing. A quick solution for this problem may be the worst solution, as a problem here indicates that we haven't put much thought into our design.
Some questions that are answered in the video:
- Why does the environment/database type matter when it comes to the transaction log?
- When discussing transactions, what is one technique mentioned that DBAs should train developers to prevent transaction log issues?
- What do I caution about custom setups?
For mastering data transformation from one form to another form, check out the highest-rated Automating ETL course on Udemy. For a coupon to the course, check out the trailer video on the channel SQL In Six Minutes.
In some cases, the log may be indicative of other problems that may not relate to design. For instance, I've been in situations where we had to deep dive into hardware issues that were the underlying cause, though the log was the red flag that helped us determine these. Unfortunately, these are much more nuanced problems and with good design, we may not determine these issues as quickly because we have to first eliminate the design as the underlying issue. I cannot stress the point of designing a SQL Server environment correctly in the beginning to significantly reduce troubleshooting later.
Are you looking for tech consultants that can assist with design and development? From building custom applications to working with existing infrastructure that's causing you trouble, we can get you connected to consultants who can assist. You can contact for assistance.
Awesome post
if you don't got the 500 Hive claim it now, 12th march is the last date to claim it.
So today is last date get it quickly click Here