Your database
Performance
Security & compliance
SQL Server heap (no clustered index)
Part of the Schema & indexes check · fix arrives as a guide
What it is
A SQL Server table is a heap — it has no clustered index.
Why it matters
Rows are stored unordered, so range scans read more pages than necessary and forwarded records accumulate as rows are updated and grow. Performance degrades with write volume rather than staying flat.
How to fix it
Add a clustered index, typically on the primary key or on the column the table is most often ranged over. Narrow, ever-increasing keys work best since the clustering key is carried in every non-clustered index.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.