Data Access Layer that allows Multiple Data Sources

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

Has anyone come across any elegant frameworks that allows writing to
multiple data sources? I'm looking for something that allows a typical
master data source for storing and retrieving data, but I'd also like
it to be able send select data to other datasources. IOW, the other
servers most likely wouldn't be a complete copy of the main data source.

As an example, we'd like to use this framework to maintain a separate
reporting server. Large reports can sometimes bog down our main
database server and it would be nice to be able to run these reports
off of a separate server that's in sync with the main server. Other
uses might be to maintain an auditing database (I work in a heavily
regulated industry) or accounting database (our customers own the main
data, but we may want to maintain a separate database of what
transactions have been processed so that we can charge them based on
use).

Does MS' Data Application Block allow for multiple data sources? Others?

Scott C.
 
John said:
Microsoft's Data Access Application Block v2 and the newer Enterprise
Library Data Access Application Block both support multiple data
Click to expand...


Thanks John. I'll take a closer look.

Scott C.
 
Scott said:
Has anyone come across any elegant frameworks that allows writing to
multiple data sources? I'm looking for something that allows a typical
master data source for storing and retrieving data, but I'd also like
it to be able send select data to other datasources. IOW, the other
servers most likely wouldn't be a complete copy of the main data source.

As an example, we'd like to use this framework to maintain a separate
reporting server. Large reports can sometimes bog down our main
database server and it would be nice to be able to run these reports
off of a separate server that's in sync with the main server. Other
uses might be to maintain an auditing database (I work in a heavily
regulated industry) or accounting database (our customers own the main
data, but we may want to maintain a separate database of what
transactions have been processed so that we can charge them based on
use).
Click to expand...

Sure, see http://www.llblgen.com :) Read data from oracle, change it,
write it back in sqlserver, pull data from sqlserver A in context 1 and
pull data from sqlserver B in context 2 etc.

Frans

--
 
Back
Top