Indexes are a common concept across many data stores, and data is stored in the form of records. Every record has a key field, which helps it to be recognized uniquely.
By convention, an index is created in each property or set of properties used as a foreign key.
Indexes cannot be created using data annotations. Instead, you can use the Fluent API to specify an index on one or more columns.
The following example specifies an index on a single column.
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder.Entity<Author>()
.HasIndex(a => a.Name);
}
You can also specify an index over more than one column.
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder.Entity<Author>()
.HasIndex(a => new { a.FirstName, a.LastName });
}
By default, indexes are not unique and multiple rows are allowed to have the same value(s) for the index's column set. You can make an index unique, as shown below.
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder.Entity<Author>()
.HasIndex(a => a.Name)
.IsUnique();
}
When you insert more than one entity with the same values for the index's column set, it will throw an exception.
By convention, indexes created in a relational database are named IX_<type name>_<property name>
. For composite indexes, <property name>
becomes an underscore separated list of property names.
You can use the Fluent API to set the name of the index created in the database.
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder.Entity<Author>()
.HasIndex(a => a.Name)
.HasDatabaseName("Index_Name");
}
In some relational databases, you can specify a filtered or partial index to index only a subset of a column's values, reduce the index's size, and improve performance and disk space usage.
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder.Entity<Book>()
.HasIndex(a => a.Title)
.HasFilter("[Url] IS NOT NULL");
}
In SQL Server provider, EF Core adds an IS NOT NULL
filter for all nullable columns that are part of a unique index. To override this convention, you can supply a null
value, as shown below.
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder.Entity<Book>()
.HasIndex(a => a.Title)
.IsUnique()
.HasFilter(null);
}