The partitioning of a relation based on an attribute can have a considerable impact on the query cost. What properties would be candidates for partitioning in the case of a workload of SQL queries on...

Extracted text: The partitioning of a relation based on an attribute can have a considerable impact on the query cost. What properties would be candidates for partitioning in the case of a workload of SQL queries on a single relation? b. Given the workload, how would you choose between the various partitioning techniques? c. Can a relation be partitioned by more than one attribute? Explain your response.