FORCESCAN

External Article

Why the SQL Server FORCESCAN hint exists

  • Article

It is often generalized that seeks are better than scans in terms of retrieving data from SQL Server. The index hint FORCESCAN was recently introduced so that you could coerce the optimizer to perform a scan instead of a seek. Which might lead you to wonder: Why would I ever want a scan instead of a seek?

2014-08-15

8,926 reads

Blogs

SQL Server is Slow, part 3 of 4

By

In parts 1 and 2 of this series, we’ve gathered info and done the...

AI Model Size, Parameters and Download

By

At SQL Saturday Boston 2025, I gave a presentation on local LLMs and there...

Expanding Your DBA Horizons: Installing PostgreSQL in a Home Lab

By

Are you diversifying your DBA skillset? My recent job search made one thing clear:...

Read the latest Blogs

Forums

caught off guard by some greek lettering in a warehouse feed

By stan

Hi we run 2019 standard.   Our warehouse's ssis based etl is klunky but so...

Unlocking High-Concurrency Inserts in SQL Server with OPTIMIZE_FOR_SEQUENTIAL_KEY

By Chandan Shukla

Comments posted to this topic are about the item Unlocking High-Concurrency Inserts in SQL...

Vector Datatype

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Vector Datatype

Visit the forum

Question of the Day

Vector Datatype

The new Vector datatype in SQL Server 2025 is a binary type that has a few parameters. What parameters are required?

See possible answers