Note: This question is part of a series of questions that present the same scenario. Each question in this series
contains a unique solution. Determine whether the solution meets the stated goals.
The Account table was created using the following Transact-SQL statement:
There are more than 1 billion records in the Account table. The Account Number column uniquely identifies
each account. The ProductCode column has 100 different values. The values are evenly distributed in the
table. Table statistics are refreshed and up to date.
You frequently run the following Transact-SQL SELECT statements:
You must avoid table scans when you run the queries.
You need to create one or more indexes for the table.
Solution: You run the following Transact-SQL statement:
Does the solution meet the goal?
A.
Yes
B.
No
Explanation:
Create a clustered index on the AccountNumber column as it is unique, not a non nonclustered one.
https://msdn.microsoft.com/en-us/library/ms190457.aspx
A Yes. The second index will avoid table scans. There was no requirement related to clustered index or uniqueness however stupid it would be that one would create these 2 indexes. The goal is to avoid table scans.
10
23