Managing Configuration Changes and Cache Behavior
Most changes to the table, view, or procedure that you are caching, or changes to your cache data storage definitions, require that you reevaluate your cache configuration. Certain changes could result in missing cache data, which would result in temporary errors for any application attempting to access the data in the cache. Performing an explicit clear or refresh action following a configuration change is recommended.
The following configuration changes are managed automatically by Studio:
• If you rename an object that you are caching or any of its parent folders, your cached tables are updated.
• If you are using the automatic caching option, Studio drops the old files and creates any necessary new files automatically.
If you change any of the following, be sure to fully reevaluate your caching configuration:
• The storage data source type, physical location, name, number of columns, or the column data types.
• The cache status table physical location, name, or other metadata.
• The number of columns or a column data type definition for the view you are caching.
• The name or number of parameters for a procedure you are caching.