Which of the following best describes horizontal partitioning in database design?
Think about dividing data by rows rather than columns.
Horizontal partitioning splits data by rows, distributing subsets of records across tables or servers.
Which option correctly explains vertical partitioning in database systems?
Focus on dividing data by columns instead of rows.
Vertical partitioning divides a table by columns, storing different columns in separate tables.
You have a user database with millions of records and many columns. You want to improve query speed for user profile info and reduce server load. Which partitioning strategy is best?
Consider which data is accessed most often and how to reduce data scanned per query.
Vertical partitioning helps by separating frequently accessed columns, reducing data scanned and improving query speed.
Which statement correctly describes a tradeoff when choosing between horizontal and vertical partitioning?
Think about how data is split and how queries might be affected.
Horizontal partitioning splits rows, improving write scalability but may require complex joins across partitions.
A table has 1 million rows and 50 columns. 10 columns are accessed frequently and 40 rarely. Each row is 1 KB total. If vertical partitioning splits the table into two tables (10 columns and 40 columns), approximately how much storage is saved when querying only the frequently accessed columns?
Consider the proportion of columns accessed and data scanned per query.
Since 10 out of 50 columns are accessed, scanning only those saves about 80% of data scanned per query.