Free tools Windows power users keep installed
One-click scans. No signup required.
To find a possible missing index, inspect the plan for expensive scans or filters, compare estimated rows with actual execution where available, and check whether an existing index can serve the query. A scan alone is not proof: it can be the cheapest choice when a query needs a large share of a table. Treat plan warnings and index suggestions as leads, then test any change against representative workload behavior.
Start with the query and its plan
Use the exact slow statement from the same database engine and environment where the problem occurs. Plan labels and fields differ between PostgreSQL, MySQL, and SQL Server, so do not interpret one engine using another engine’s terminology.
Read the complete plan, not just the scan node. Find the operations that process the most rows or consume substantial time, then trace how filters, joins, sorting, and aggregation contribute. A scan followed by a selective filter can be worth investigating; a scan that returns most of a table may be entirely reasonable.
Compare estimates with what execution actually did
Estimated row counts show what the optimizer expected. Where supported, actual execution data shows what happened. A large gap between the two can point to stale statistics or data distributions the optimizer has not modeled well. Investigate that gap before assuming an index is the remedy.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
PostgreSQL’s EXPLAIN ANALYZE reports actual row counts and timing alongside estimates. It executes the statement, and profiling adds overhead, so interpret its timings accordingly. MySQL’s EXPLAIN ANALYZE, introduced in MySQL 8.0.18, also executes the statement and reports iterator timing information.
Read plans by database engine
PostgreSQL
PostgreSQL presents a plan as a tree. The lower nodes access tables through operations such as sequential, index, or bitmap index scans; higher nodes may join, aggregate, or sort their results. Work upward from the access nodes and note where rows are filtered or multiplied.
A Seq Scan is not inherently a missing-index signal. PostgreSQL can prefer it when the query needs all or many rows. If a sequential scan applies a selective filter and reads far more rows than it returns, inspect the predicate, existing indexes, and row estimates together. For runtime evidence, use EXPLAIN (ANALYZE, BUFFERS), remembering that analysis executes the statement and incurs profiling overhead. Keep table statistics current so the planner has useful estimates.
MySQL
In MySQL’s EXPLAIN output, inspect the table’s type, possible_keys, key, rows, filtered, and Extra fields.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
possible_keyslists indexes that may be relevant to finding rows;keyidentifies the index actually selected. They answer different questions.- A
NULLpossible_keysvalue means MySQL identified no relevant index for finding rows. Check the query’sWHEREconditions and the schema; this output does not prescribe an index. - A
NULLkeymeans the optimizer found no index it considered more efficient for executing that query. rowsis an estimate, not a count of rows guaranteed to be read. Compare it with actual execution information where available.
If an index is unexpectedly unused, MySQL documents ANALYZE TABLE as a way to update key-distribution statistics. Recheck the plan after updating them where appropriate.
SQL Server
An estimated execution plan shows optimizer output without running the query; an actual execution plan includes runtime information. SQL Server may display missing-index suggestions, but those are leads rather than complete index designs. Microsoft advises reviewing all missing-index requests for a table together with its existing indexes before adding one. Check for overlap and consider the workload, including the cost of maintaining additional indexes during writes.
Rank #4
- Used Book in Good Condition
Check the schema and the optimizer’s information
Before proposing an index, inspect the indexes that already exist and compare their key columns with the query’s actual filtering, join, and ordering requirements. A scan label does not reveal the right index definition or key-column order by itself.
Also check whether the optimizer has current, useful statistics. PostgreSQL relies on statistics in pg_statistic to estimate data and choose plans. MySQL’s documented ANALYZE TABLE command can refresh key distributions when an index is unexpectedly not chosen. An estimate that is far from actual execution is a reason to assess statistics and data distribution, not to add an index automatically.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Validate an index candidate against the workload
- Record a baseline. Save the exact query, its plan, and representative execution behavior in the environment that matters.
- Form a specific hypothesis. Identify the predicate, join, or ordering operation an index is meant to help, and confirm that no suitable existing index serves it.
- Review the trade-off. Consider overlap with current indexes and the cost of maintaining another index for writes and storage.
- Make one considered change at a time. Avoid treating every scan or automated recommendation as an instruction to add an index.
- Re-run and compare. Check the new plan and representative behavior against the baseline. Plan choices and estimates can vary with engine version and data, so judge the change in the relevant workload rather than from a plan label alone.
What a query plan can—and cannot—tell you
A plan can show how the optimizer accesses rows, which estimates informed that choice, and, in actual plans, what execution did. It can expose a plausible index opportunity, an estimate problem, or a plan that is already appropriate. It cannot, by itself, prove that an index is missing or supply a universally correct index definition. The right decision depends on the SQL, schema, data distribution, engine version, and workload.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
