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

Monday Monitor Tips: Configuring Access to the MCP Server

By

I have been experimenting with MCP servers in a few ways, including the Redgate...

The GO Barrier: Why SSMS Multi-Server Query Waits for the Slowest Connection

By

I deployed a schema change to 30 servers using multi-server query and deploy-at-low-priority. Small...

10 Things I Hate About Fabric Deployment Pipelines— And Some Alternatives

By

Fabric deployment pipelines look like they solve CI/CD for Fabric content, especially for people...

Read the latest Blogs

Forums

A Challenge of Our Knowledge

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Challenge of Our Knowledge

The memory toll of VARCHAR(MAX) in SQL Server

By sabyda

Comments posted to this topic are about the item The memory toll of VARCHAR(MAX)...

Transaction Log Truncation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Transaction Log Truncation

Visit the forum

Question of the Day

Transaction Log Truncation

In SQL Server 2025, where can I find information about items that prevent or delay the transaction log truncation?

See possible answers