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,819 reads
User Defined Functions is a new feature in PowerBI currently in public preview. There...
By ChrisJenkins
There are some fundamental boxes that your reporting system must tick. ✅ The figures...
By Chris Yates
When it comes to managing complex database environments, having the right monitoring solution is...
Has anyone used Azure SQL MI on the next-gen general purpose tier, Microsoft documentation...
Comments posted to this topic are about the item Create an HTML Report on...
Comments posted to this topic are about the item The Last Good DBCC Run
I want to check when DBCC CHECKDB was last run on my Baseball database. What code should I use?
See possible answers