Hello Akash,
we have/had the same issues regarding the transport of catalog objects. In our case virtual tables and not triggers, but the problem is the same.
We "solved" it in the following way to reduce/avoid the manual effort on the target systems:
- The creation of the catalog objects (in our case virtual tables) is implemented in a stored procedure (hdbprocedure) which can be transported. The implementation makes, before the object is created, a check if the object already exists or changes were done. Only in case it does not exist or changes were done the object is created/recreated.
- All our stored procedured creating catalog objects are called within a "central" stored procedure.
- This "central" stored procedure is called on the target systems by an XSJOB (xscron). The definition of the job is also transported. On the target systems the job is scheduled to run every hour. With that (beside the scheduling of the xsjob) no manual activity is necessary anymore on the target systems, because the catalog objects are created by the scheduled stored procedure execution.
Best Regards,
Florian