The following questions are intended to reinforce key information presented in this chapter. If you are unable to answer a question, review the appropriate lesson and then try the question again. You can find answers to the questions in the Appendix, 'Questions and Answers.'
Can a clustered index also be a unique index?
If you query a Customers table containing a clustered index on the primary key column, CustomerID, and a nonclustered index on the LastName column, is the nonclustered index a covering index for the following Transact-SQL statement?
SELECT LastName, CustomerID FROM Customers WHERE LastName LIKE 'nej'
Is a composite index key always part of a covering index?
How does the global fill factor affect existing indexes and new indexes where a fill factor is not specified?
How do you maintain a fill factor in existing indexes?
What type of index can assist the following query?
SELECT productname FROM products WHERE productname LIKE '%tool'
You create the following composite index:
CREATE UNIQUE CLUSTERED INDEX index01 ON employees(socialsecuritynumber, lastname)
Is Index01 ideal for the following query? Explain your answer.
SELECT socialsecuritynumber, lastname FROM employees WHERE lastname = 'kaviani'
Why is it unwise to create wide, clustered index keys?
Which index type, clustered or nonclustered, must be most carefully designed? Explain your answer.
If a table contains a single nonclustered index, what is its bookmark?
What is the default sort order for an index key?
You wish to create a nonclustered index on a view in SQL Server 2000 Enterprise Edition, but an error message is returned indicating that you cannot create a nonclustered index on the view. What is the most likely reason for this error message?