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,831 reads
By Brian Kelley
If you are considering any of the ISACA AI certs like the Advanced Artificial...
By ChrisJenkins
Are you currently using Microsoft Fabric or considering migrating to it? If so, there...
By SQLPals
Track SQL Server Configuration Changes Using the Error Log If you...
WhatsApp:0817866887 Jl. Sunset Road No.88B, Kuta, Kec. Kuta, Kabupaten Badung, Bali 80113
Tlp/Wa_Cs:0817-866-887 Jl. Raya Puputan No.10, Panjer, Denpasar Selatan, Kota Denpasar, Bali 80226
Tlp/Wa_Cs:0817-866-887 Jl. Pangeran Diponegoro No.15, Petisah Tengah, Kec. Medan Petisah, Kota Medan, Sumatera Utara...
In the Database Engine, when a deadlock is detected, what does the detection interval shrink to (in time)?
See possible answers