Database creation and selection in MySQL - Time & Space Complexity

Time Complexity: Database creation and selection

O(n)

Understanding Time Complexity

When we create or select a database, the system performs some work behind the scenes.

We want to understand how this work grows as the number of databases increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

CREATE DATABASE example_db;
USE example_db;
    

This code creates a new database named 'example_db' and then selects it for use.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking if the database name already exists and registering the new database.
• How many times: This check happens once per database creation, not repeated in a loop.

How Execution Grows With Input

As the number of databases grows, the system needs to check existing names to avoid duplicates.

Input Size (number of databases)	Approx. Operations
10	About 10 checks
100	About 100 checks
1000	About 1000 checks

Pattern observation: The work grows roughly in direct proportion to the number of existing databases.

Final Time Complexity

Time Complexity: O(n)

This means the time to create a database grows linearly with the number of databases.

Common Mistake

[X] Wrong: "Creating a database always takes the same time no matter how many databases exist."

[OK] Correct: The system must check existing databases to avoid duplicates, so more databases mean more checks.

Interview Connect

Understanding how simple commands scale helps you explain system behavior clearly and shows you think about efficiency.

Self-Check

"What if the system used a fast lookup like a hash table to check database names? How would the time complexity change?"