Generally, you will have no need to worry about the number of virtual log files in your transaction log. However, if you use the default settings for 'auto-grow', you can end up with such 'fragmentation' in your transaction log as to affect performance noticably. How can this be avoided? How can you tell it's a problem? What do you do about it? Greg explains.
2012-11-23 (first published: 2012-05-01)
7,126 reads
2010-08-16 (first published: 2010-03-05)
3,810 reads
By gbargsley
Hello, reader! Today, I’m going to walk you through a scenario that many DBAs...
By Chris Yates
The Castle and the Keys Imagine your Azure SQL environment as a sprawling digital...
By Steve Jones
I think we might have forgotten this a bit, but on one of the...
Hi all, this is my first time posting on this forum, thank you all...
We are using MySQL version 5.6 in our Windows Server 2012 R2 environment. We...
We have created a parent table, child table & Audit log table in SQL...
I run this command on my SQL Server 2022 database:
ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON;What is the default data retention period? See possible answers