, kettch wrote

However, as was said, you most likely don't need all of those at once.

Whatever the result, the issue is not with EF. Sounds to me like someone went mad with denormalisation.

Conceptually how you deal with a model with 800 classes is going to be hard, you would be best to group the tables by functionality, or refactor the database if it is young