hvt said:
Martin, as the question was posted:
can JDBC send that to two different databases...
this can be done by maintaining two different connection/statement
object. I 've tried this for searching Weblogic portal repository and
local application data through Lucene. Weblogic maintains it's portal
repository data in pointbase (default database) and local application
data was maintained in Oracle9i.
If you see any problem in this please clarify.
There's no problem with simply connecting to two or more databases as
long as you're only reading them and you have no need for data
consistency between the databases.
However, if you're updating tables in one or more databases or if
updates applied to one database are dependent on the content of other
databases you have a potential problem. You can't guarantee that all
updates are either committed or rolled back without using a transaction
manager to enforce consistency across all the databases.
The downside is that a transaction within the transaction manager will
hold locks in all the databases your transaction accesses until all
databases have successfully committed the transaction. If such a
transaction is long running it can have a major impact on the
performance and response times of the underlying databases.
Note that the consistency issue arising from just connecting to several
databases (i.e. not using a transaction manager) can be a problem for BI
applications despite them being read-only: if one database is updated
while you're retrieving data it could make the data set you're analyzing
inconsistent. Visualize the situation where online stock control is
being used, but supplier and customer accounts are only updated
periodically: there's no way a BI application will get a consistent
snapshot during the day. This the reason many organizations use data
warehouses to support their BI systems. Once data is extracted from the
operational databases and loaded into a data warehouse you know its
consistent and will remain so until the next snapshot is extracted.
HTH