Can you shrink your transaction log files to death?
can undermine server performance. An expert runs various tests to determine how transaction log file size responds to various T-SQL commands.
2009-02-23
3,627 reads
Transaction Log
Transaction Log Growth, do you need it?
One of the most common questions asked about SQL Server has to do with the transaction log and why does it grow. James Rea brings us a good explanation here of what happens and what you should do about it.
2010-05-28 (first published: 2009-01-05)
32,735 reads
Help! My SQL Server Log File is too big!
Over the years, I have assisted so many different clients whose transactional log file has become "too large" that I thought it would be helpful to write about it. The issue can be a system crippling problem, but can be easily avoided. Today I'll look at what causes your transaction logs to grow too large, and what you can do to curb the problem.
2008-10-28
6,699 reads
SQL Server Sanity: Maintain Healthy Transaction Logs for Easy Data Recovery
Learn how executing frequent backups and maintaining healthy transaction logs in SQL Server leads to quick recovery. Failing to do so can mean having to re-enter a lot of data.
2008-10-20
3,238 reads
Blogs
The Book of Redgate–Being Reasonable
By Steve Jones
As a part of the Book of Redgate, we have a series of (red,...
Azure Data Factory Pipeline Debugging Fails with BadRequest
I recently had a new pipeline fail. It was actually a copy of an...
Unlocking Real-Time Financial Insights: The Power of Microsoft Fabric
By Chris Yates
Microsoft Fabric is transforming real-time analytics for financial institutions. It provides a unified data...
Forums
Joining against min date only
This is one of those things very hard (for me)to explain in words. See...
Feeling your age? How would you know?
Comments posted to this topic are about the item Feeling your age? How would...
Sever Migration
Hi, one of my server configured with Standard_D64ds_v4 what is next level of version...
Question of the Day
Rolling Back CUs
Can I rollback a cumulative update and remove it from my SQL Server instance?
See possible answers