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,825 reads
By DataOnWheels
Ramblings of a retired data architect Let me start by saying that I have...
By Steve Jones
A customer was testing Redgate Data Modeler and complained that it auto-generated PK names....
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
Hi everyone, Below is a consolidated summary of what we validated Architecture & data...
Hi all, I recently moved to a new employer who have their HA setup...
Comments posted to this topic are about the item Semantic Search in SQL Server...
I have this data in a SQL Server 2025 table:
CREATE TABLE Response ( ResponseID INT NOT NULL CONSTRAINT ResponsePK PRIMARY KEY , ResponseVal VARBINARY(5000) ) GOIf I want to get a value from this table that I can add to a URL in a browser, which of these code items produces a result I can use? See possible answers