Previous Topic: SQL-Defined Databases and CachingNext Topic: Controlling the Cache


Non-SQL-Defined Databases and Caching

Non-SQL-defined databases do not have timestamps for automatically determining whether a database's definition accurately describes the underlying data. Consequently, when changing the structure of a non-SQL-defined database, it is the administrator's responsibility to ensure that all SQL statements impacted by the change are recompiled. If dynamic SQL caching is not used, then this entails recompiling access modules that reference the affected database. If dynamic SQL caching is used, then it also entails purging the cache of statements that reference the affected database. This can be done by deleting rows from the SYSCA.DSCCACHE or SYSCA.DSCCACHEV tables.

Note: For more information about these tables, see the CA IDMS SQL Reference Guide.

It is also recommended that dynamic SQL caching be disabled during the transition period in which the definitional changes are being implemented. For information on how to do this, see Controlling the Cache.

CA IDMS will detect the need to recompile cached SQL statements if a change is made to the referencing SQL schema through which a non-SQL-defined schema is referenced. It does this by comparing the update stamp of the referencing SQL schema to the compile stamp of the cached statement.