System.Web.UI.WebControls Namespace SqlDataSource Class
.NET Framework version 2.0
Sets or retrieves the cache expiration behavior that, when combined with the duration, describes the behavior of the cache that the data source control uses.
| Inline |
<asp:SqlDataSource cacheexpirationpolicy = enumValue ... > |
| Script |
SqlDataSource.CacheExpirationPolicy [ = enumValue ] |
The property is read/write with no default value.
The SqlDataSource control supports data caching. While data is cached, the Select method retrieves data from the cache rather than from the underlying database. When the cache expires, the Select method retrieves data from the underlying database, and then caches the data again.
The behavior of the cache is determined by a combination of the CacheDuration and CacheExpirationPolicy settings. If the CacheExpirationPolicy property is set to the Absolute value, the SqlDataSource caches data on the first data retrieval operation, holds it in memory for the amount of time that is specified by the CacheDuration property, and then discards it after the time has lapsed. The cache is then refreshed during the next operation. If the CacheExpirationPolicy property is set to the Sliding value, the data source control caches data on the first data retrieval operation, but resets the time window that it holds the cache for each subsequent operation. The cache expires, if there is no activity for a time that os equal to the CacheDuration value since the last Select operation.
The SqlDataSource control can cache data only when in the DataSet mode. A NotSupportedException exception is thrown by the Select method, if the SqlDataSource control is set to the DataReader value and caching is also enabled.
NOTE: When you are using client impersonation under Microsoft Windows authentication, the data is cached when the first user accesses the data. If another user requests the same data, the data is retrieved from the cache. The data is not retrieved by making another call to the database to verify the user's access to the data. If you expect more than one user to access the data, and you want each retrieval to the data to be verified by the security configurations for the database, do not use caching.
