nerdexam
Microsoft

70-463 · Question #226

You are designing a data warehouse that uses SQL Server 2012. You are preparing to update the contents of a fact table that contains a non-clustered columnstore index. You need to run an update statem

The correct answer is D. Drop the columnstore index.. In SQL Server 2012, non-clustered columnstore indexes are read-only and do not support DML operations directly. The index must be dropped before performing updates.

Design and implement a data warehouse

Question

You are designing a data warehouse that uses SQL Server 2012. You are preparing to update the contents of a fact table that contains a non-clustered columnstore index. You need to run an update statement against the table. What should you do first?

Options

  • APause the columnstore index.
  • BChange the recovery model of the database to Bulk-logged.
  • CChange the non-clustered columnstore index to be a clustered columnstore index.
  • DDrop the columnstore index.

How the community answered

(57 responses)
  • A
    7% (4)
  • B
    4% (2)
  • C
    12% (7)
  • D
    77% (44)

Why each option

In SQL Server 2012, non-clustered columnstore indexes are read-only and do not support DML operations directly. The index must be dropped before performing updates.

APause the columnstore index.

There is no 'Pause' operation available for columnstore indexes in SQL Server 2012; this is not a valid index management option.

BChange the recovery model of the database to Bulk-logged.

Changing the database recovery model to Bulk-logged affects transaction logging behavior but does not enable DML operations on tables with non-clustered columnstore indexes.

CChange the non-clustered columnstore index to be a clustered columnstore index.

Changing a non-clustered columnstore index to a clustered columnstore index is a different structural change and does not resolve the read-only restriction in SQL Server 2012.

DDrop the columnstore index.Correct

SQL Server 2012 non-clustered columnstore indexes are read-only, meaning any INSERT, UPDATE, or DELETE operation against the table will fail while the index exists. You must drop the index, perform the DML operation, and then recreate the index afterward.

Concept tested: SQL Server 2012 non-clustered columnstore index read-only limitation

Source: https://learn.microsoft.com/en-us/sql/relational-databases/indexes/columnstore-indexes-overview

Topics

#columnstore index#fact table#index management#SQL Server 2012

Community Discussion

No community discussion yet for this question.

Full 70-463 Practice