*Result*: Dynamic Caching & ADO DataSets.

*The paper considers the use of incremental queries for fetching data dynamically. As a part of the .NET Framework, ADO.NET provides the DataSet class whose primary goal is to represent an in-memory data cache. Objects that can be cached include tables, views and constraints. The key to a dataset cache that retrieves data dynamically is with the adapter. When using a Structured Query Language query, one cannot randomly access retrieved records and one should not expect the fill function to do things differently. Data retrieval has to start from the beginning. In the limited data scenario, the caching function emphasizes saving network traffic and increasing the speed of data retrieval. The implementation hides many tasks, such as database connection management, rebuilding the incremental query string and getting the total number of rows in the query. When a query result becomes too large it may be impossible to hold it in memory. If large data returns are the problem, however, the first thing to try is narrowing the query result. Every now and then, when the quantity of data within a dataset exceeds a limit, one have to drop some to keep the in-memory data size manageable. An in-memory cache for large database queries is often necessary.*