DP-203 · Question #254
DP-203 Question #254: Real Exam Question with Answer & Explanation
The correct answer is B: The history table is created as a rowstore table. An anonymous history table is automatically built in the same schema as the temporal or current table. The history table is built as a rowstore table. If possible, page compression is applied on the history table otherwise the table remains uncompressed. For example, few table co
Question
You need to create a quick object in a test environment and therefore you decide to create a temporal table with an "anonymous" history table. From the given below statement/remarks about the history table in this context, choose the statement(s) that is/are true.
Options
- AYou need to manually create the anonymous history table and provide its specific schema
- BThe history table is created as a rowstore table
- CThe history table is created as a columnstore table
- DA default clustered index is developed for the history table
- EA history table is always uncompressed. No compression is ever applied on the history table
Explanation
An anonymous history table is automatically built in the same schema as the temporal or current table. The history table is built as a rowstore table. If possible, page compression is applied on the history table otherwise the table remains uncompressed. For example, few table configurations, like SPARSE columns, don't allow compression. Option A is incorrect. An anonymous history table is automatically built in the same schema as the temporal or current table. Option B is correct. It is true that the history table is built as a rowstore table. Option C is incorrect. The history table is created as a rowstore table, not columnstore table. Option D is correct. A default clustered index is developed for the history table with an auto- generated name with the format IX_<history_table_name>. This index has the PERIOD columns Option E is incorrect. It is not true that the history table always remains uncompressed. If possible, page compression is applied on the history table otherwise the table remains uncompressed. For example, few table configurations, like SPARSE columns, don't allow https://docs.microsoft.com/en-us/sql/relational-databases/tables/creating-a-system-versioned- temporal-table?view=sql-server-ver15
Community Discussion
No community discussion yet for this question.