When you bind or unbind an object, all the object’s pages that are currently in the cache are flushed to disk (if dirty) or dropped from the cache (if clean) during the binding process.
The next time the pages are needed by user queries, they must be read from the disk again, slowing the performance of the queries.
Adaptive Server acquires an exclusive lock on the table or index while the cache is being cleared, so binding can slow access to the object by other users. The binding process may have to wait until transactions complete to acquire the lock.
The fact that binding and unbinding objects from caches removes them from memory can be useful when tuning queries during development and testing.
If you need to check physical I/O for a particular table, and earlier tuning efforts have brought pages into cache, you can unbind and rebind the object. The next time the table is accessed, all pages used by the query must be read into the cache.
The plans of all stored procedures and triggers using the bound objects are recompiled the next time they are run. If a database is bound to the cache, this affects all the objects in the database.