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
In a previous blog post we went through how to build a Docker container...
Businesses are drowning in data, but starving for insights. That's where SQL experts swoop...
By Brian Kelley
The bottom line here is this: the idea that a CSP takes care of...
Have anyone implemented CDC, and if so, what has been your experience with it?...
I'm getting a error when using the Import and Export wizard to copy tables...
I have joined a new project, where the business uses Azure SQL Hyperscale for...
What are the initial config sizes for the tempdb primary data files, secondary data files, and log files in SQL Server 2022?
See possible answers