Identify and fix why the GEAR2 system database account can only be used when deploying app

[hatfieldjm4]

It is hard coded somewhere in the database, possibly on a trigger related to the tech catalog data or on the obj_technology object. I believe the database account name is hard coded into this trigger which is preventing other database accounts to be used, if needed (for example, using your personal database account to deploy locally).

[hatfieldjm4]

The system account is hard coded into triggers on the following objects (that I could find so far). These triggers exist to create insert/update logs, but there may be more uses than simply logging that I'm unaware of.

• obj_technology
• zk_technology_poc
• obj_cuicategory
• obj_datacenters
• obj_contracts
• tp_SoftwareRelease
• tp_SoftwareVersion
• tp_SoftwareProduct
• tp_SoftwareLifecycle
• tp_Manufacturer