page

SQLServerCentral Article

How Bad are Bad Page Splits – The Rest of the Story

  • Article

In Part 1 of this article we looked at a specific use case (probably exaggerated) that gave us an idea about how CPU and IO performance might be affected by a bad page split. We continue this analysis looking at what really happens to the data on the leaf pages of a clustered index with […]

4 (3)

You rated this post out of 5. Change rating

2020-07-02

4,372 reads

Blogs

Extending a SQL Server Failover Cluster Across Regions in  Google Cloud Platform (GCP)

By

I was the principal author of this SIOS whitepaper, which describes how to build...

Heading to 2024 PASS Summit

By

I am able to head back to Seattle for the PASS Summit this year....

Tell me the positives of your solution

By

I still have a tendency to talk about all the cons of a proposed...

Read the latest Blogs

Forums

The Cloud Security Problem

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Cloud Security Problem

Virtualizing AWS data by using Fabric Shortcuts: Data Engineering with Fabric

By John Miner

Comments posted to this topic are about the item Virtualizing AWS data by using...

Timescale Brings PostgreSQL into the GenAI Era with pgai Vectorizer

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Timescale Brings PostgreSQL into the...

Visit the forum

Question of the Day

The LAGging NULL

I have this data in a SQL Server 2022 table:

player         yearid team HR
Alex Rodriguez 2012   NYY  18
Alex Rodriguez 2013   NYY  7
Alex Rodriguez 2014   NYY  NULL
Alex Rodriguez 2015   NYY  12
Alex Rodriguez 2016   NYY  9
If I run this code, what are the results returned in the hrgrowth column?
SELECT
  player
, yearid
, hr
, hr - LAG (hr, 1, 0) IGNORE NULLS OVER (ORDER BY yearid) AS hrgrowth
FROM dbo.playerstats;

See possible answers