Cardinality Estimates

External Article

Fixing Gatekeeper Row Cardinality Estimate Issues

  • Article

The Query Optimiser needs a good estimate of the number of rows likely to be returned by each physical operator in order to select the best query plan from the most likely alternatives. Sometimes these estimates can go so wildly wrong as to result in a very slow query. Joe Sack shows how it can happen with SQL Queries on a data warehouse with a star schema.

2012-12-10

1,163 reads

Blogs

Getting the SQL Server MCP Server Running

By

If you’ve wanted a SQL Server MCP server for your databases, it’s available. The...

Introducing azsql-migration-test: Test and Validate Azure SQL Database Migrations

By

Introducing azsql-migration-test, a small open-source CLI that validates your Azure SQL Database migrations against...

Rambling about Data on Wheels – origins, branding, expansion

By

I have been asked many times about how the name “Data on Wheels” came...

Read the latest Blogs

Forums

Make It Routine

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Make It Routine

DBCC CHECKDB Limits III

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits III

CROSS APPLY Fundamentals: Part 1

By Imran2629

Comments posted to this topic are about the item CROSS APPLY Fundamentals: Part 1

Visit the forum

Question of the Day

DBCC CHECKDB Limits III

On SQL Server 2025, does DBCC CHECKDB support Memory-Optimized tables?

See possible answers