# Eliminate `TableFullScan` by using a Composite Index

![`smart`](TuningIndexByExplainAnalyze03_en_001_20230129.png)

------------------------------------------------------------------------------
After creating a multi-column index on the `HIRE_DATE` and `GENDER` columns, the `EXPLAIN ANALYZE` output shows no `Selection` operators. This indicates that all filtering operations have been pushed into the index scan, and no additional filtering is required. Consequently, the performance of the SQL statement should improve.

It's important to note that the multi-column index should be created as (`GENDER`, `HIRE_DATE`) rather than (`HIRE_DATE`, `GENDER`). This is because the `WHERE` clause includes a range query on `HIRE_DATE`. In a multi-column index, placing `HIRE_DATE` first would prevent the `GENDER` column from being effectively used for filtering. This concept will be covered in more detail in later chapters.