We are using a 'corporate' version of the data warehouse but need to
add additional 'local' tables and columns to the database structure.
This will then necessitate applying additions/modifications to the
issued catalog. [We are using specific prefixes to ensure there is no
clash of names]



I have now been warned by the central development team that I will
encounter problems in the future, i.e. when they issue an upgrade to
their system and I add back in the modifications I have made locally.



I am told this is because Cognos issues internal ids for the items
defined within the catalog and these are used in Impromptu, etc. to
identify the specific data items referenced within the report(s).



When changes are applied to the catalog, there is a risk that particular
internal ids will now point to a different item in the database.



Can anyone clarify if I really do have a (potential) problem. If so,
what are the recommendations of how to minimise the affect of this
difficulty.


--
Posted via http://dbforums.com

I don't believe the catalog in fact contains "internal id's", Cognos cubes
do.

What you will find is the qualification being a problem. If you qualify all
of your tables less in the catalog before moving to production Impromptu
should simply call the table name and columns required rather than a fully
qualified version. To verify how your sql is qualified go to the catalog
menu and choose tables. You should see a qualification tab, try qualifying
less (all the way, at the highest level) and then switch to the production
db. You could then test to ensure that the tables verify against the
production instance. Cheers.

ya


"w860098" <member37780 (AT) dbforums (DOT) com> wrote