Query patterns that cause collection scans in MongoDB - Step-by-Step Execution

Concept Flow - Query patterns that cause collection scans

Receive Query

↓

Check for Indexes

↓

Use Index

↓

Return Results

↓

End

The database receives a query, checks if an index can be used, and if not, performs a collection scan to find matching documents.

Execution Sample

MongoDB

db.users.find({ age: { $gt: 30 } })

Query to find users older than 30, which may cause a collection scan if no index on 'age' exists.

Execution Table

Step	Action	Index Available?	Operation	Documents Examined	Result
1	Receive query { age: { $gt: 30 } }	Unknown	Check indexes	0	Proceed
2	Check if index on 'age' exists	No	Decide operation	0	No index found
3	Perform collection scan	No	Scan all documents	1000	Filter documents with age > 30
4	Return matching documents	No	Return results	N/A	Documents with age > 30
5	End query execution	No	Complete	N/A	Query finished

💡 No index on 'age' found, so collection scan examines all 1000 documents.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
indexExists	Unknown	False	False	False
documentsExamined	0	0	1000	1000
matchingDocuments	0	0	Variable	Variable

Key Moments - 2 Insights

Why does the query scan the entire collection instead of using an index?

Because the execution_table row 2 shows no index exists on the 'age' field, so the database must scan all documents.

Does the collection scan check every document?

Yes, as shown in execution_table row 3, all 1000 documents are examined to filter those matching the condition.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the database decide to perform a collection scan?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check the 'Operation' and 'Index Available?' columns in execution_table row 2.

According to variable_tracker, how many documents are examined during the collection scan?

A 1000

B 0

C 500

D Variable

💡 Hint

Look at 'documentsExamined' after Step 3 in variable_tracker.

If an index on 'age' existed, which step would change in the execution_table?

A Step 1 would skip

B Step 3 would use index instead of collection scan

C Step 4 would not return results

D Step 5 would be removed

💡 Hint

Refer to the 'Operation' column in execution_table rows 2 and 3.

Concept Snapshot

Query patterns without matching indexes cause collection scans.
Database checks for indexes first.
If no index, scans all documents.
Collection scans are slower on large data.
Create indexes on queried fields to avoid scans.

Full Transcript

When a MongoDB query runs, the database first checks if an index exists for the queried field. If an index is found, it uses it to quickly find matching documents. If no index exists, the database performs a collection scan, meaning it looks at every document in the collection to find matches. For example, querying users with age greater than 30 without an index on 'age' causes a collection scan. This scan examines all documents, which can be slow for large collections. To improve performance, create indexes on fields used in queries.