This is a dedicated watch page for a single video.
Identify the missing word(s) in the following sentence within the context of Microsoft Azure. Index design is a little bit art and a little bit science. A narrow index with few columns in its key requires less time to update and has lower maintenance overhead; however it may not be useful for as many queries as a wider index that includes more columns. When planning your indexes for a table, you should keep a few basic principles in mind: Understand the workloads of the system. A table that is used mainly for insert operations will benefit [A] from additional indexes than a table used for data warehouse operations that are 90% read activity. Understand what queries are run most frequently , and optimize your indexes around those queries Understand the data types of the columns used in your queries. Indexes are ideal for [B] types, or unique or non-null columns. Create [C] indexes on columns that are frequently used in predicates and join clauses, and keep those indexes as narrow as possible to avoid overhead. Understand your data size/volume – A table scan on a small table will be a relatively cheap operation and SQL may decide to do a table scan simply because it is easy (trivial) to do. A table scan on a very large table would be very costly.