Does accessing spatial type geometry with SQL trigger geodatabase behavior?
Accessing the information in a geodatabase by way of SQL allows external applications to access the tabular data managed by the geodatabase. These external applications may be nonspatial database applications or custom spatial applications developed in an environment other than ArcObjects. Be aware, though, that SQL access to the geodatabase bypasses geodatabase functionality, such as topology, networks, terrains, or other class or workspace extensions.
It may be possible to use DBMS features such as triggers and stored procedures to maintain the relationships between tables needed for certain geodatabase functionality. However, executing SQL commands against the database without taking this extra functionality into account, for example, issuing INSERT statements to add records to a business table, circumvents geodatabase functionality and possibly corrupts the relationships between data in the geodatabase.