You work as a database administrator at Domain.com. The Domain.com network consists of a single Active Directory domain named Domain.com. Your duties at Domain.com include administrating a SQL Server 2005 database named Certkiller -DB09.
Certkiller -DB09 contains a database named CK_Sales that stores sales transactions for the company. The table structure for the CK_Sales database is shown in the following exhibit:
The Invoices table contains more than 300 million rows of information. In this table some information is historical and some is current. You want to partition the information in order to increase performance and optimize maintenance of the CK_Sales database.
What should you do?
A.
You should implement vertical partitioning in order to increase the performance and optimize maintenance.
B.
You should implement horizontal partitioning in order to increase the performance and optimize maintenance.
C.
You need to implement Distributed partitioning in order to increase the performance and optimize maintenance.
D.
You should implement a raw partition in order to increase the performance and optimize maintenance.
Explanation:
Table and index partitioning – intended to improve performance of operations performed on large tables. The basic concept is straightforward and involves splitting a table into several units (called partitions), which can be accessed independently of each other, limiting impact of I/O intensive activities performed on the table’s data (queries, data loads, backups and restores, maintenance tasks – such as index rebuilds and defragmentations, as well as operations that would result in lock escalation to the table level). The most common method of splitting data is horizontal partitioning, in which rows of a table matching mutually exclusive criteria (such as, range of dates or letters in alphabet, for datetime and character data, respectively) are placed in designated partitions.