1

We currently have separate databases per application but I am finding more common tables (ex. countries, employee type) for each database that are replicated. I am considering created a separte lookup database to store all these "lookup" tables. The application databases would then reference the same key in the lookup table which would not only save some space but also allow for cross application/database queries.

Is there an flaw to this design? I don't think I've ever seen it online but most samples online are bound to a single database. The only drawback that comes to mind is the inability to add relationships since that is bound to other tables in the same database. The other issue is .net specific in that I think this would make using the Entity Framework more difficult if not impossible.

pretzelb
  • 1,131
  • 2
  • 16
  • 38

1 Answers1

0

I don't think EF allow to connect with multiple databases, But if your database support Synonyms, than its possible , this link might help you.

Below is one more link which might help you to how EF can work with multiple databases.

Thanks Suresh

Community
  • 1
  • 1
Suresh
  • 1,131
  • 1
  • 15
  • 28
  • Thanks for pointing out the workarounds on the EF issue. But looking back I think my basic question might be too vague or subjective. – pretzelb Apr 26 '14 at 01:24