1

Closed

Designer: All primary keys should be clustered (affects SQL Azure)

description

I designed an entity data model with two entities between which there exists a many to many relationship. When I auto-generate SQL code to generate the database for this model, it has generated a table (two columns) to keep track of this many-to-many association. However, this table has a PRIMARY KEY NONCLUSTERED on both columns.

This is extremely annoying because I've to do manual workarounds to deal with this issue, when supposedly the sql generated by the EF is azure compatible.

Issue was already reported in stackoverflow.
http://stackoverflow.com/questions/3567946/entity-framework-many-to-many-clustered-vs-nonclustered-index

Can you please fix this with urgency?
Thanks
Closed Apr 18, 2013 at 2:03 AM by nathangr

comments

RoMiller wrote Oct 16, 2012 at 6:45 PM

We agree this is an issue that needs to be fixed, we've marked this issue to be fixed in the EF6 release.

krzysztof_zaven wrote Dec 18, 2012 at 5:30 PM

It would be great to see that ASAP :). I hope You can do something about it guys.

RoMiller wrote Jan 16, 2013 at 9:26 PM

We are planning to fix this in EF6. The workaround is to edit the script before running it.