Table definition is
CREATE TABLE Sales.SalesOrderHeaderBig(
 SalesOrderID int IDENTITY(1,1) NOT NULL,
 RevisionNumber tinyint NOT NULL,
 OrderDate datetime NOT NULL,
 DueDate datetime NOT NULL,
 ShipDate datetime NULL,
 [Status] tinyint NOT NULL,

Yes, the lag function can offset more than row.  Syntax is (from Microsoft):

January 14, 2019 at 3:02 pm

#2018883

Wow, didn't know the article was going to generate a fire-storm on TSQL syntax.  The original purpose was to see if there was a difference getting max/min value of a...

Actually all the suggestions made are good ones, and as most have pointed out all is very environment sensitive.  90% of the DelFlag column are marked 'N' and the others...

Index work had already been accomplished -- hence the index + key lookup.  The query returns every column in the table, and I am just opposed to creating a non-clustered...

Same query plan, same cost, same IO, same cpu time.  No change defining it as a variable first.

From the estimated query plan.  Statistics were up to date, so estimated rows were close to actual rows.

I noticed that also when using a columnstore index as a clustered index and a non-clustered Hash Primary Key (for in-memory tables). When using dm_db_xtp_hash_index_stats I get one row...

Hmmm, you finally put in writing (and script) what I have been doing for years. Yeah! Great work!

Interesting topic. After retiring from the Air Force I started in management and eventually ended up as a CTO for an insurance company here in Texas. After a...

I was an early user of SQL LiteSpeed. Yes you are correct, the less IOs offerred by compression resulted in tremendously less backup and restore times. Although depending...

Makes it even more interesting if you add following:

insert into @test-2 values ( NULL )

Answer is still 6.

Data presentation -- still an art, definitely not a science. The Challenger accident is a significant occurrence where we had the data, but was never presented in a way...

Well written for what it covered, but my initial expectation before reading the article was that you would touch more on techniques for handling transaction log growth and also handling...