Row and Page Compression for Azure SQL Database

Correct Answer: E

Row and page compression can be configured on the following database objects:

Option A is incorrect.

You can configure row and page compression not only on a whole nonclustered index but all given database objects.

Option B is incorrect.

Row and page compression can be configured not only on a whole indexed view but all given database objects.

Option C is incorrect.

Row and page compression can be configured not only on A whole table that has been stored as a heap but also all given database objects.

Option D is incorrect.

Row and page compression can be configured not only on A whole table that has been stored as a clustered index but also all given database objects.

Option E is correct.

Row and page compression can be configured for all the given database objects.

Reference:

To know more about Data Compression, please visit the below-given link:

Sure, I'd be happy to explain the answer in detail.

Azure SQL Database provides the option of data compression to decrease the size of the database. Data compression can help reduce the amount of disk space required to store data, which can lead to faster backup and restore operations, lower storage costs, and improved query performance.

In Azure SQL Database, there are two types of compression that can be used: row compression and page compression. Row compression compresses individual rows of data, while page compression compresses entire data pages. Both types of compression can be used together or separately, depending on the needs of the database.

Now, let's consider the given options and identify the database objects on which row and page compression can be configured:

A. A whole nonclustered index: Row compression can be applied to a nonclustered index. When row compression is applied to a nonclustered index, each index row is compressed individually.

B. A whole indexed view: Page compression can be applied to an indexed view. When page compression is applied to an indexed view, the data pages used by the view are compressed.

C. A whole table that has been stored as a heap: Row compression can be applied to a heap. When row compression is applied to a heap, each row of data in the heap is compressed individually.

D. A whole table that has been stored as a clustered index: Both row and page compression can be applied to a table that has been stored as a clustered index. When row compression is applied to a clustered index, each index row is compressed individually. When page compression is applied to a clustered index, the data pages used by the index are compressed.

Therefore, the correct answer to the question is option E, as all of the given objects (nonclustered index, indexed view, table stored as a heap, and table stored as a clustered index) can be compressed using row and/or page compression.