How to add nonclustered indexes in Entity Framework db-first project?

Question

I have a table in SQL Server which includes custom nonclustered indexes for some columns. And I have also a project with below versions.

.Net Framework 4.6.2
Entity Framework 6.4.4

I added an entity data model to project based on my existing database (using a database-first approach).

Although a SELECT query returns quickly in database, the same query gets a timeout error in the project. And I thought that EF couldn't add column indexes to the project. I searched index names in the project, but there isn't any code about indexes in the project.

So, how can I add indexes to my database-first model?

The indexes aren't added to EF - if anything, they would be added in the SQL Server database..... From EF, you'd have to use migrations to do something like this (change/modify the structure of the database) — marc_s
– marc_s, Commented Nov 29, 2021 at 9:10
You could just add a migration and execute arbitrary SQL in the migration, including a "create index...". — Wiktor Zychla
– Wiktor Zychla, Commented Nov 29, 2021 at 9:19
It's really unclear what you're asking, mainly because you seem to have a wrong perception of what indexes are and where they play a role. Stick to the problem: differences in performance. Are you executing exactly the same SQL query as EF does? — Gert Arnold
– Gert Arnold, Commented Nov 29, 2021 at 9:37
Database first means you create the database first, including any indexes. there isn't any code about indexes in the project. there wouldn't be. You don't write any index-specific code in your SQL query after all. — Panagiotis Kanavos
– Panagiotis Kanavos, Commented Nov 29, 2021 at 14:13
the same query gets a timeout error in the project what does your code do? How much data is there? — Panagiotis Kanavos
– Panagiotis Kanavos, Commented Nov 29, 2021 at 14:16

David Browne - Microsoft · Accepted Answer · 2021-11-29 14:03:29Z

1

So, how can I add indexes to my database-first model?

"database-first" means that you apply design changes to the database first, and then apply any changes to the EF model second.

So you just create the indexes in SQL Server using Visual Studio or SSMS, and since EF model doesn't need to change when you add an index, you're done.

answered Nov 29, 2021 at 14:03

David Browne - Microsoft

90.7k7 gold badges52 silver badges87 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

How to add nonclustered indexes in Entity Framework db-first project?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related