rationale for ad hoc
Duke Ganote, March 03, 2008 - 1:45 pm UTC
For my product *IX link-to-HS-link-to-production DB2, it's easy enough to build views for all the production tables. They're fixed, and in one schema.
However, for our test *IX database, it points to a test/dev DB2 database where one schema is 'as is' database, another is 'to be next release' with a few more columns on some tables, and so forth. Those are the ones where it would be more convenient to allow the developers to ad-hoc against any DB2 schema from *IX, rather than logging into the Wind'Oracle database to run ad hocs against DB2.
I suppose I could build (there's no overlap in schema namespace) schemas on the HS database for all of the dozen or so DB2 dev/test schemas, and overnightly rebuild views so they'd capture any overnightly changes to the DB2 schemas, yet still be ad hoc accessible to the deveopers from Oracle on *IX.