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,912 reads
By Arun Sirpal
AgentDBA began as a command line. That suits one DBA on one server, but...
By Steve Jones
I have a few Azure subscriptions, which are fairly small and not used that...
This post shows you how to install containerd as the container runtime for Kubernetes...
Wa:083849450961 Jl. Ahmad Yani No.39 A, Rw1, Sidokumpul, Kec. Sidoarjo, Kabupaten Sidoarjo, Jawa Timur...
Telp/Wa 62817825533 Jl. HZ. Mustofa No.300, Tuguraja, Kec. Cihideung, Kota Tasikmalaya, Jawa Barat 46124
Telp/Wa 628218200203 Bank Bca Kcu Purwakarta, Jl. Jendral Sudirman No.85, Nagri Tengah, Kec. Purwakarta,...
With regard to SQL Server 2025's Vector support, what is an embedding?
See possible answers