We all love Gupta SQLBase for its speed, efficiency, power and small footprint. And Gupta TeamDeveloper for processing all that data once it arrives at the client.

But sometimes Network traffic or bandwidth or high-pressure load from thousands of requests on the database server can hamper all that great work that SQLBase does to get you your data on time. 

Here’s a neat way to relieve some of the strains on your network - reducing the bottleneck and allowing SQLBase the freedom to do its thing.

Its obvious to some, but not to all, that caching (holding) static data (data that doesn’t change) locally on the client machine, saves all those thousands of round trips from each client machine to the remote database server and back.

Here’s a way to help out….. Static data can be loaded from the remote database server into a local (on the client computer) SQLite database on start up.  The SQLite database (or ‘cache’) can be held in local memory (RAM) with absolutely no disk I/O (no reading from the hard disk). When any ‘lookup’ or static data is required by your TeamDeveloper application, it can be read from local memory using SQL in the usual way – but no network traffic, no local disk I/O ( all held in RAM ), no Server I/O (except on app start-up or a ‘Refresh’ option) and so improve response time/server load/application speed.

I have used SQLite as a cache for static data in a few applications now, and it makes so much sense to help out a high demand -high load system in this way.