DRAG DROP
You administer a Windows Azure SQL Database database used for data warehouse operations.
The database contains a table named OrdersHistory, defined as follows:
A weekly ETL (extract-transform-load) runs a large INSERT statement to add data into the
OrdersHistory table. The process is taking a long time to complete. You discover that the
bulk of the process is performing non-clustered index updates on the OrdersHistory table.
You need to improve the performance of the ETL process faster. You need to meet the
following requirements:
Avoid losing existing permissions on existing objects.
Use minimal administrative effort.
What should you do? (To answer, move the appropriate actions from the list of actions to the
answer area and arrange them in the correct order.)
Answer: See the explanation.
Note:
* Drop and rebuild the index, then run the insert statement.
* Rebuilding an index can be executed online or offline. Reorganizing an index is always
executed online. To achieve availability similar to the reorganize option, you should rebuild
indexes online.
Incorrect:
* Dropping and rebuilding the OrdersHistory table would lose the permissions on this table.
* The SELECT INTO statement creates a new table and populates it with the result set of the
SELECT statement.
— Disable all Indexes
ALTER INDEX ALL ON [dbo].[EmployeesNew] DISABLE
— Insert new data
Run the INSERT statement
— Enable all Indexes
ALTER INDEX ALL ON [dbo].[EmployeesNew] Rebuild
http://blog.sqlauthority.com/2010/05/12/sql-server-understanding-alter-index-all-rebuild-with-disabled-clustered-index/
agree
I agree with NB’s comment
I agree too,
my information-base :
https://www.simple-talk.com/sql/learn-sql-server/bulk-inserts-via-tsql-in-sql-server/
and further :
https://msdn.microsoft.com/en-us/library/ms188388%28v=sql.110%29.aspx
I agree too
Agree as well.
Disable
Insert
Rebuild