ansaurus

Question

Answer 1

+2 A:

A co-worker found a thread on another site [social.msdn.microsoft.com] that discusses this same issue. One discussed solution was to perform all joins in views in the "primary" database, and expose those views as objects in the application. That will probably work in my situation, since the majority of my data is in one database, and the small number of tables in the other databases are read-only.

MikeWyatt 2009-12-15 23:12:54

Answer 2

+1 A:

This is going to sound a little crazy, but I just tested it, so try this:

Create a custom entity class for the "external" table you want to join to, or use SqlMetal to generate the class;
Go to the TableAttribute, which should say something like [Table(Name="dbo.ExternalTable")], and change it to [Table(Name="DatabaseTwo.dbo.ExternalTable")]

Create a partial class with the same name as the "DatabaseOne" DataContext, and add your Table<T> property there, i.e.:

partial class DatabaseOneDataContext
{
    public Table<ExternalTableRow> ExternalTable
    {
        get { return GetTable<ExternalTableRow>(); }
    }
}

And now try running your entire query off of the first DataContext:

DatabaseOneDataContext context = new DatabaseOneDataContext();
var query = from s in context.RealTable
            join t in context.ExternalTable
              on s.ID equals t.ID
            select new { s, t };
Console.WriteLine(query.ToList().Count);

Unbelievably, it works. It's not quite as simple as just using SqlMetal, but you only need to write the partial class once, then you can just run SqlMetal on both databases and change the TableAttribute of any external tables to include the database name.

It's not perfect, but it's 95% there, no?

Aaronaught 2009-12-15 23:52:06

This is interesting, but it would still require a bit of work to fully automate (as you said). I'll give it a shot if creating views in the main DB doesn't work out.

MikeWyatt 2009-12-16 14:06:20

You could probably write a short script that you just feed the two CS files (generated by SqlMetal) and the table names you want to "import", and have it automatically generate the partial class and entities. The former is a text template, the latter is just a string.Replace, so you'd end up with something totally automated. But if you control the databases and don't mind creating cross-database views, then that will be easier to manage in the long haul.

Aaronaught 2009-12-16 15:21:55

ansaurus

tags:

views:

answers:

DataContext across multiple databases

related questions