Entity Framework – how to manage tables in different databases but on the same server?

I am using SQL Server 2008.

It seems as though in EF I need a different entity context for each database. Joining tables between databases means having to allow for this which is inconvenient and makes it more likely that I would simply put everything in one database.

  • Calling a stored procedure python
  • SELECT TOP is slow, regardless of ORDER BY
  • Connect to domain SQL Server 2005 from non-domain machine
  • `0` values are not shown when I put a string value filter SQL
  • “SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED” and views
  • Move multiple row values in a single row in SQL
  • Am I missing something? Surely EF can work better than this?

  • Strategy for storing supplemental data alongside imported data
  • SQL - How to store and navigate hierarchies?
  • Relationship of Primary Key and Clustered Index
  • Sharing a table row between users in SqlServer Azure
  • cascading deletes causing multiple cascade paths
  • How to implement referential integrity here?
  • 2 Solutions collect form web for “Entity Framework – how to manage tables in different databases but on the same server?”

    You could map your entities to a view that returns joined tables, so your EF model doesn’t know about all this technical DB stuff.

    I don’t think it’s properly supported, but this guy has managed to get it to work.

    Basically, she set up Synonyms for the databases, and hacked the edmx file.

    MS SQL Server is a Microsoft SQL Database product, include sql server standard, sql server management studio, sql server express and so on.