List managed tables

1. Start a database command prompt session and connect to the staging or authoring database.

2. Issue one of the following SQL commands...

   Option	Description
   Site data	select tabname from STGSITETAB
   Merchant data	select tabname from STGMERTAB
   Mixed site and merchant data	select tabname from STGMRSTTAB

Some of the managed tables returned by the SQL commands do not have staging triggers associated with them. Any changes that we make to these tables in the staging database are not captured in the STAGLOG table. When you run the stagingprop utility, changes in these non-staged tables are not propagated from the staging database to the production database.

To view a list of tables that contain staging triggers, issue the following SQL command:

• (DB2) select trigname, tabname from syscat.triggers where trigname like 'STAG%'

  The list of tables with staging triggers can be found in the tabname column of the result set.

• (IBM i) select trigger_name, event_object_table from qsys2.systriggers where trigger_name like 'STAG%'

• Oracle select object_name from user_objects where object_type = 'TRIGGER' and object_name like '%STG_%;

  For Oracle staging triggers, it has this format:

  <X>STG_tableName

  ...where:

  • X = I for insert, U for update, or D for delete

  • tableName = the name of the table that owns the trigger.

Related tasks
Creating a database table filter list
Filtering data for the stagingprop utility to propagate