No there is no way to control SQL code first generates - it is code first and its current philosophy (the bad one actually) is: you know nothing about the database and you don't bother.
No there is no way to control SQL code first generates - it is code first and its current philosophy (the bad one actually) is: you know nothing about the database and you don't bother. The only way to change this behavior is to write custom database initializer, use custom database queries to search for created index, remove that index and create a new one. Some references: How to stop EF4.1 Code-First to create Culstered index for the entity PK Custom initializer with adding an index Example of more advanced initializer The initilizer will make your solution dependent on the concrete database server product.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.