Performance and Tuning

External Article

How Filters and Sorting can Derail SQL Pagination Performance

  • Article

In my previous tip, Pagination Performance in SQL Server, I showed how to make SQL pagination more predictable – turning O(n) into O(1). I materialized and cached row numbers to page through instead of calculating them on every request. It wasn’t the whole story, though; real pagination queries rarely get to sort without filtering. Users always want more control, and filtering can threaten that predictability.

2026-02-06

Blogs

What Does It Mean to Make Data AI-Ready?

By

Making Data AI-Ready, Part 1 (This is the first article in a three-part series...

Using the Data API Builder–VS Live San Diego Resources

By

Thanks for attending my sessions. Resources below: Slides: Using Data API Builder GitHub repo: ...

Running a Local LLM On Your Laptop Resources

By

Thanks to everyone that attended my sessions at VS Live San Diego yesterday. It...

Read the latest Blogs

Forums

Having some performance issues with linked server query

By LearningDBA

When I run my query from DW, which uses a linked server, it times...

Implementing Type 4 Slowly Changing Dimensions in SQL Server

By Dinesh Asanka

Comments posted to this topic are about the item Implementing Type 4 Slowly Changing...

The Disabled Index

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Disabled Index

Visit the forum

Question of the Day

The Disabled Index

I run this code on SQL Server 2022.

CREATE TABLE Drink
(
    drinkid INT NOT NULL
        CONSTRAINT DrinkPK PRIMARY KEY CLUSTERED,
    drinkname VARCHAR(20),
    rating NUMERIC(2, 1)
)
GO

INSERT INTO Drink
(
    drinkid,
    drinkname,
    rating
)
VALUES
(1, 'Margarita', 4.5),
(2, 'Mojito', 4.3),
(3, 'Old Fashioned', 4.7),
(4, 'Martini', 4.4),
(5, 'Cosmopolitan', 4.2)
GO
ALTER INDEX drinkpk ON dbo.drink DISABLE
GO
SELECT * FROM dbo.Drink
GO
What is the result?

See possible answers