Comments on: Using Fluent NHibernate With Legacy Databases

By: Rod Paddock

Rod Paddock — Fri, 02 Jul 2010 15:06:01 +0000

@cloggins The normal NHibernate workflow does not normally specify the Schema() and Table() attributes on a mapping. These are derived from the model. Generally these attributes are only used when accessing pre-existing databases (aka legacy)

By: cloggins

cloggins — Fri, 02 Jul 2010 01:03:13 +0000

Am I missing something? Where’s the legacy stuff. As best I can tell, this is just basic ‘use Fluent NHibernate to connect to a database’ stuff.

By: Rod Paddock

Rod Paddock — Tue, 29 Jun 2010 16:32:43 +0000

@Yonkz. Thanks for the heads up on that. I forgot about linked servers. Proably because we tried using linked servers in the past and were never happy with the results. Too much flakieness IMO.

By: Yonkz

Yonkz — Tue, 29 Jun 2010 14:58:35 +0000

I successfully use the .Schema() method to use two different SQL servers, but the catch is that they need to be set up as Linked servers. This creates some other interesting issues surrounding MSDTC, and forces you to have two separate instances of SQL Server running in your development environments, due to the fact that Microsoft no longer supports distributed transactions in a loop back scenario.