Changes and Implications

All settings are instantiated when a database connection is made. The connecting program can explicitly send these settings in code. If the connecting program does not send the connection settings, the database defaults are used. When you create a database, the server defaults will be copied to the database defaults. You can also change the database defaults afterwards.

Some settings are stored in the code of an object. The value of the setting as stored in the code is the value the setting had during object creation. When the connection setting changes at a later stage, the object still behaves as if the setting had the initial value.

Changing a setting might cause a query to behave differently. You can create code that makes it behave the same, regardless of the settings.

Where necessary, Isah changed the code in stored procedures, functions, triggers and views. However, you still need to check the customization code and change it, if required. In Appendix 1, all constructions that can give rise to different behavior are summed up, as well as an alternative that does not change the behavior. Please, use this list as a guideline for making your customization code ANSI safe.