SQL COUNT(*) Becomes Expensive on Large Tables – Bits of .NET

SQL

SQL COUNT(*) Becomes Expensive on Large Tables

- 11.01.26 - ErcanOPAK

Simple query, big cost.

Why
Full table scan required.

Fix
Maintain approximate counters when possible.

Related posts:

SQL Tip: "NULL" should not be compared directly

Why NVARCHAR(MAX) Can Destroy Query Plans

List all Foreign Keys referencing a given table in SQL Server

Post Views: 7

Leave a Reply Cancel reply