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,781 reads
By Steve Jones
This is my last week of the year working (I guess I come back...
By Steve Jones
This is my last week of the year working (I guess I come back...
I recently read the book Agile Data Warehouse Design – Collaborative Dimensional Modeling, from...
I have an ADF pipeline that copies Files from source to destination. Both Source...
Comments posted to this topic are about the item Function Defaults
I have created this function in SQL Server 2022:
CREATE FUNCTION dbo.AddInt (@one INT, @two INT = 1) RETURNS INT
AS
BEGIN
RETURN @one + @two
END
How can I call this and invoke the default value for @two? See possible answers