Entity framework database first best practice for managing a DB

asp.net-mvc ef-database-first entity-framework-6

Question

i would like to know if there is someone that can help me find the best way to manage a db with 50 tables that i assume has to be structured in my mvc application as multiple EMDX files for performance but that will have multiple connection strings that i hate.

So let's make a short example: i have a join of 5 tables to create a customer list grid and another 3 tables join for an employee grid.

I created two edmx context files to manage each grid and i have 2 connection strings.

Now, if i haev to create 30 grid will i have to create 30 edmx files and corresponding 30 connection strings?

The question is: is this the best practice for this? duplicating 30 times the connection string that connects to the same db?

Thanks

1
0
10/20/2015 12:45:12 PM

Popular Answer

I am not sure why you need separate connection string. If you are connecting to same database then one connection string is enough.

Also if i understand correctly you are creating separate edmx file for each grid. This is not correct way of using Entity Framework. You should be using only one EDMX file for a database, 50 tables is not a big number. If you have complex query then i'll suggest to use store procedure and call it via Entity Framework using function import

1
10/20/2015 12:54:48 PM


Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow