Use Clustered Index on Primary Key when using BaseIdentityIdEntity

Using a non clustered index on the primary key makes sense for the reasons described in the documentation when using UUID as a primary key. However to me, it makes less sense when using BaseIdentityIdEntity. Since inserts will sequential, I think it would make sense to use a clustered index when using BaseIdentityIdEntity. I could be wrong, but I believe there would be enhanced performance when selecting from the database or doing reporting, especially if the database becomes sufficiently large.

You are absolutely right, we should create a default clustered key if the type of ID is different from UUID. See the linked YouTrack issue.

Thank you for the idea!

1 Like

:ticket: See the following issue in our bug tracker: