How SQLCache Works

SQLCache's tunable caching technology stores frequently requested data where it is needed most, on the server requesting the content. This means that as long as the cached data's Time To Live (TTL) has not expired the server will use its local copy with no request made of the remote data server. If the TTL has expired then the data is refreshed. When refreshing its cache SQLCache issues the request and receives the data. Therefore, the request is a single instance per front-end server and not multiple requests made on behalf of many different clients. The number of connections made to the remote data server is thereby drastically reduced.

As previously stated, SQLCache uses fully tunable caching technology, which means its cache can be tuned in accordance to how often the data changes. The cached data is given a Time To Live (TTL) parameter, which is used to determine how many seconds the data can be used before it requires refreshing.

SQLCache has three tuning levels (Global, Service and Specific) to accommodate all circumstances and provide you with fine grain control. Global tuning applies to all requests for data that use the SQLCache data provider and which are not covered in either the Service Level, or Specific SQL Command tuning parameters. Service level tuning applies to all commands made to a single data source (for example, a single database) and which are not specified in the Specific SQL Commands. Specific SQL Command tuning enables you to set the TTL for specific requests for data (normally SQL command statements). Commands specified at this level override all other levels of tuning.

SQLCache's operation can easily be described using the example of delivering dynamic web content using Microsoft's ADO. With traditional ADO each SQL command involves a "round trip" to the database server. This is depicted below.

BEFORE SQLCache

When SQLCache is installed and used on the web server there is no need for the SQL command to query the database server (if the TTL of the record is still valid). Instead SQLCache provides the data direct for use in building the web page. This is illustrated below.

AFTER SQLCache