Why partition a large table by date?

• A. To improve query performance and maintenance by restricting scans.
• B. To randomize data.
• C. To duplicate data across partitions.
• D. To reduce the need for indexes.

Answer: (A)

Partitioning a large table by date groups rows into date-range segments, so the system can treat each date range as a separate piece of data. The key benefit is that queries filtered by date can skip entire partitions that don’t match the filter, a process called partition pruning. This means far less data to read, reducing I/O and speeding up responses, especially on very large tables.

It also helps with maintenance. You can archive, move, or drop old partitions without touching the rest of the table, making data retention and cleanup much more efficient. As new data arrives, it goes into new partitions, keeping ongoing organization straightforward. While partitioning can improve overall performance, you still need appropriate indexes to speed up searches within partitions, and partitioning does not duplicate data across partitions or eliminate the need for indexing.