sql server - Multiple SQL Databases with EF - Good or Bad design? -
currently have large in house platform makes use of number of different sql databases (all on same server). have created new databases feel data quite different/independant storing in other databases. approach have ended having number of different databases (most have 30-50+ tables), inevitably there connections required between them.
as using entity framework, cross database queries proving real pain, have tried number of different approaches , feel main problem ef doesn't work across multiple databases.
while know answer "it depends" i'm interested in peoples ideas or views on question
should combine of our seperate databases 1 large database?
were correct have split our data different databases (even if ef doesn't work it)?
how large database talking about? how many tables / how many gbs? type of data goes in?
the answer guessed "it depends". here i'd no, splitting not right choice. if having cross database queries, data split not correct. might better split across databases in scenarios data independent - transactional , reporting, example (but of course requires data sync 1 other).
have considered separating data in same database, residing on different schema? done.
Comments
Post a Comment