How to use an application database without touching its schema -
if have application uses data of existing database , needs more, , don't want change schema of existing database, how do that?
background of question: use ibm product (connections) store user profiles. have lots of custom requirements (lots of custom fields , logics), create few more tables, views , functions in backend database of connections store custom data. however, ibm's internal database , not supposed touch it, when upgrade connections, our custom tables, views , functions gone.
so decide move out our custom things. problem still need join data connections. (or not database join, other way integrate data before presenting users. )
if create federated table in our own database, can create tables , views used to. have performance issues? , still going heavily depend on ibm's schema , have assume don't change it. approach?
what other options consider?
if create federated table in our own database, can create tables , views used to. have performance issues?
probably. application code have joins between ibm database tables , database tables.
i'm assuming connections uses db2. if bring own db2 database, think can sql joins between 2 separate db2 databases.
either way, code should reside in separate data access package made of data access objects. rest of applications use data access package.
and still going heavily depend on ibm's schema , have assume don't change it.
ibm change schema, , have plan on making corresponding changes database , / or application.
what other options consider?
you copy ibm data database database. still have make changes copy process when ibm schema table definitions change.
Comments
Post a Comment