18 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Misztur, Chris commented  ·  March 06, 2012 10:23  ·  Flag as inappropriate  ·  Delete

  Openquery over linked servers would be awesome! Thanks for EF thus far.

• Anonymous commented  ·  February 18, 2012 13:41  ·  Flag as inappropriate  ·  Delete

  The sooner the better

• Miroslav Kovacevic commented  ·  January 30, 2012 09:30  ·  Flag as inappropriate  ·  Delete

  We need this for yestarday.

• Ewald commented  ·  January 20, 2012 04:12  ·  Flag as inappropriate  ·  Delete

  Yes, we need this for larger applications.

• Vai commented  ·  November 20, 2011 06:11  ·  Flag as inappropriate  ·  Delete

  This is extremly required for enterprise projects. We need to use multiple db on the single mssql server.
  Please add this feature as soon as possible you can.

• Al commented  ·  September 20, 2011 06:33  ·  Flag as inappropriate  ·  Delete

  This is required for enterprise project development. We are currently using multiple db's with MS SQL on single db server. We are also using synonym and merging edmx files.as a work-around. Please add this feature.

• Vinz commented  ·  September 05, 2011 11:00  ·  Flag as inappropriate  ·  Delete

  A direct mapping of synonyms is required. One of Entity Framework's claims is that it works best with Microsoft SQL Server, so this is expected. Although there are ways of merging edmx files together that's not a direct approach which we expect to have when using the Entity Framework

• Arkadiusz Kaminski commented  ·  August 19, 2011 06:45  ·  Flag as inappropriate  ·  Delete

  It'd be great if this feature was implemented in EF. I'd reduce lots of hassle with creating views / store procedures to bypass that limitation.

  On the other hand: while developing multi database enterprise solutions you may look into the SOA approach.

• Joseph commented  ·  August 10, 2011 00:53  ·  Flag as inappropriate  ·  Delete

  The sooner we get this the better...

• Ladislav Mrnka commented  ·  July 17, 2011 09:30  ·  Flag as inappropriate  ·  Delete

  "Without having to manage database objects - linked servers ..." That is totally out of scope of ORM. You should always have to do that even if cross database mapping will be supported. There is a big difference between cross database and cross server queries.

• Ray commented  ·  June 22, 2011 08:56  ·  Flag as inappropriate  ·  Delete

  We need this feature now.

• Rachel commented  ·  May 28, 2011 09:24  ·  Flag as inappropriate  ·  Delete

  If your database supports Synonyms, it is possible to make an EF model span multiple databases. EF doesn't treat a Synonym any different than it would a regular database table, so you can merge two edmx files and it will treat the 2nd database as part of the first one providing the synonyms are setup. I wrote about how to do it in the following link, which includes scripts for generating synonyms and merging edmx files. http://rachel53461.wordpress.com/2011/05/22/tricking-ef-to-span-multiple-databases/

• David C commented  ·  April 12, 2011 13:46  ·  Flag as inappropriate  ·  Delete

  This is a must

• Marcel Roma commented  ·  February 09, 2011 00:22  ·  Flag as inappropriate  ·  Delete

  Most enterprises today have very heterogenous and fluctuant data environments. Beeing able to span an abstract model across several data sources would definitely make EF the product of choice when it comes to data access modelling and also would increase EF's rate of adoption.

• Utku Ozan ÇANKAYA commented  ·  November 27, 2010 14:35  ·  Flag as inappropriate  ·  Delete

  This is a MUST to develop enterprise applicaions.

• Daniel G commented  ·  November 10, 2010 11:51  ·  Flag as inappropriate  ·  Delete

  This is essential for enterprise development. Please do not overlook this.

• Matt Hall commented  ·  September 17, 2010 01:49  ·  Flag as inappropriate  ·  Delete

  I have seen this requirement come in from a number of clients.

• Tony Fabrikant commented  ·  September 14, 2010 06:33  ·  Flag as inappropriate  ·  Delete

  This is a very real need for a lot of existing applications. The ability to expand the data model over more than one database will finally make EF the best option for a lot of projects. Having the entities from multiple dbs in one cohesive graph will streamline development and result in much cleaner code.