Which three actions should you perform in sequence?

DRAG DROP
You are building a fact table in a data warehouse.
The table must have a columnstore index. The table cannot be partitioned.
You need to design the fact table and load it with data.
Which three actions should you perform in sequence? (To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.)

DRAG DROP
You are building a fact table in a data warehouse.
The table must have a columnstore index. The table cannot be partitioned.
You need to design the fact table and load it with data.
Which three actions should you perform in sequence? (To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.)

Answer:



Leave a Reply 4

Your email address will not be published. Required fields are marked *


luis conceição

luis conceição

1. Create Table
2. Load Data
3. Create coloumnstore index

Slazenjer_m

Slazenjer_m

luis is absolutely right. xVelocity is not a requirement for Columnstore indexing. It’s just an option for improving querying on column-wise indexes. An xVelocity memory optimized columnstore index, groups and stores data for each column and then joins all the columns to complete the whole index. This differs from traditional indexes which group and store data for each row and then join all the rows to complete the whole index.

So, you must do the following first even if you want to implement xVelocity-type columnstore indexes…

1. Create the Fact table (the most-basic requirement for data load)
2. Load the data
3. Create the columnstore index.

Milen

Milen

Actually the index can be prepared before loading data – so the order

1. Create the Fact table (the most-basic requirement for data load)
2. Create the columnstore index.
3. Load the data

is also right

Rami

Rami

Milen, As per my understanding, you need to load the data first as you cannot change data for Columnstore index.