Gets or sets the cache expiration behavior that, when combined with the duration, describes the behavior of the cache that the data source control uses.
Documentation for this section has not yet been entered.
The System.Web.UI.WebControls.SqlDataSource control supports data caching. While data is cached, the SqlDataSource.Select(System.Web.UI.DataSourceSelectArguments) method retrieves data from the cache rather than from the underlying database. When the cache expires, the SqlDataSource.Select(System.Web.UI.DataSourceSelectArguments) 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 SqlDataSource.CacheDuration and SqlDataSource.CacheExpirationPolicy settings. If the SqlDataSource.CacheExpirationPolicy property is set to the System.Web.UI.DataSourceCacheExpiry.Absolute value, the System.Web.UI.WebControls.SqlDataSource caches data on the first data retrieval operation, holds it in memory for the amount of time that is specified by the SqlDataSource.CacheDuration property, and then discards it after the time has lapsed. The cache is then refreshed during the next operation. If the SqlDataSource.CacheExpirationPolicy property is set to the System.Web.UI.DataSourceCacheExpiry.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 is equal to the SqlDataSource.CacheDuration value since the last SqlDataSource.Select(System.Web.UI.DataSourceSelectArguments) operation.
The System.Web.UI.WebControls.SqlDataSource control can cache data only when in the SqlDataSourceMode.DataSet mode. A NotSupportedException exception is thrown by the SqlDataSource.Select(System.Web.UI.DataSourceSelectArguments) method, if the System.Web.UI.WebControls.SqlDataSource control is set to the SqlDataSourceMode.DataReader value and caching is also enabled.
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.