Binding an object to a cache retains the object in memory and can expediate processing, keeping the bound objects in memory to avoid having any physical I/O when they are referenced.
The named cache must exist, and its status must be “Active.”
The database or database object must exist.
To bind tables, indexes, or objects, you must be using the database where they are stored.
To bind system tables, including the transaction log table syslogs, the database must be in single-user mode.
To bind a database, you must be using the master database.
To bind a database, user table, index, text object, or image object to a cache, the type of cache must be “Mixed.” Only the syslogs table can be bound to a cache of “Log Only” type.
You must own the object or be the database owner or the system administrator.
Binding objects to caches is dynamic; you need not restart the server.
sp_bindcache cache_name, dbname [,[owner.]tablename [, indexname | "text only" ] ]
sp_bindcache pubs_cache, pubs2, titles
sp_bindcache pubs_cache, pubs2, titles, titleind
sp_bindcache pubs_cache, pubs2, "fred.sales_east"
sp_bindcache pubs_log, pubs2, syslogs
sp_dboption pubs2, single, true
sp_bindcache pubs_cache, pubs2, au_pix, "text only"
sp_bindcache tempdb_cache, tempdb
You can rebind objects without dropping existing bindings.
Dirty reads are active on the object.
A cursor is open on the object
In addition, SAP ASE must lock the object while the binding or unbinding takes place, so the procedure may have a slow response time, because it waits for locks to be released.