How do custom stored procedures, triggers, and functions impact the supportability of an enterprise geodatabase?

Custom database objects, including stored procedures, triggers, and functions, are not part of the enterprise geodatabase architecture and are not tested as part of Esri's standard testing and validation processes. Organizations may choose to implement such database customizations; however, they are responsible for ensuring that the custom logic does not interfere with geodatabase functionality, ArcGIS workflows, or data integrity.

When troubleshooting issues involving an enterprise geodatabase, Esri may require that custom database objects be disabled, removed, or otherwise isolated as a potential source of the issue before further investigation can proceed.