entity framework - Do rowversion/timestamp columns in SQL Server need a nonclustered index when using EF code-first? -

all of tables have rowversion column ef uses optimistic concurrency checking. should create nonclustered index on column faster data retrieval? each table has clustered primary key named id. whenever updating data, ef/sql try locate row based on id first , run rowversion check?

none of query plans seek on column. writes performed filtering on primary key columns causes seek on index provides primary key. rowversion index never helps.

to answer such questions empirically, compare execution plans , without index in question.