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,763 reads
By Will Assaf
I recently reviewed, worked on, and added a similar example to the DATETIMEOFFSET Microsoft...
Database administrators (DBAs) are the backbone of data-driven organizations. If you're looking to break...
By Brian Kelley
Another security fundamentals topic is authentication versus authorization. For those who have a clear...
Comments posted to this topic are about the item The Backup File Extension
Comments posted to this topic are about the item Ingest and Retrieve data from...
Comments posted to this topic are about the item The DBAccountant
I run this command in SQL Server 2022. What is the extension of the backup file?
BACKUP DATABASE HerdofTwo TO DISK = 'HerdOfTwo_20240501'See possible answers