In Memory Driver

The Soft Velocity Memory driver is a new file driver technology that does not use physical tables for working with data. This is due to a RAM-based technology known as IMDD (In-Memory Database Driver). All data is stored in Random Access Memory (RAM), which gives the driver a number of unique properties:

Extremely high performance. Once data is loaded into the MEMORY table, either at program startup or on-demand, all access is virtually instantaneous.
You are also only limited by your machines memory capacity, and because you can use VIEWs to populate MEMORY tables, and can create VIEWs across multiple MEMORY tables, you have the capacity of storing and working with significant amounts of hierarchical data.
The MEMORY driver has a standard file driver interface, so you can use Memory tables with any Clarion entity or template that works with files (Browse, FileDrop, Report, etc.).
The application developer can choose to locate highly dynamic or frequently referenced tables in memory, while leaving the less intensively used parts of the database to be stored on much cheaper disk.
Provides highly exclusive data access. Storing data in a MEMORY table you can be sure of its security and privacy. Even two programs simultaneously running on the same computer will each use their own data copy.
It is especially useful for WEB-enabled applications. In addition all stored data will be automatically be destroyed when application terminates and you will never have any undeleted temporary files.
As MEMORY files are recreated each time an application runs, you don't need to convert MEMORY tables after a change to the record structure of your physical file.
Can be used as a "Global" lookup table, but unlike a global queue, you do not have to write code to synchronize threaded access, because synchronization is built into the driver.
Instantaneous access to data, even when changing the sort order or applying filters.
Like an ALIAS structure, the MEMORY driver can emulate the structure of any defined file in the dictionary, but unlike the ALIAS, it can be modified with additional columns and indexes without the need for conversion.
You use standard file processing statements with a MEMORY file as you would with other file formats.

Here are just some possible tasks for the Memory driver.

Use it as a Temporary table for Parent-Child relations where the end user makes all changes to the Child in the Memory table. For example new order items can be added and updated, and only when the invoice is actually saved, write all the child records to the physical file in a single transaction along with the order record.
Use it as a buffer for receiving SQL query results. After you have received the result set into the Memory table you can do sorting, filtering, perform QBE/QBF requests using standard browse box tools, without any additional access to the SQL server. This approach can dramatically reduce network traffic and frees server resources as fast as possible.
Using the MEMORY driver allows you to minimize the number of KEY and INDEX files in your physical tables. For example if you have a rarely requested report that requires a special index you can declare this index in the MEMORY table but not in the physical table. This way you can reduce required database resources and speed up data I/O operations.
You can reduce key and index number in your physical tables and also eliminate the need for file conversions. When you need to add a new key or index for a Report or Browse. Just add the new INDEX to the MEMORY table.
You can construct your Memory table using several data sources, and the sources can combine data tables of various formats. For example, you can load configuration data from a mainframe file and combine it with additional items from a local file.

Visit SoftVelocity's website.

If you require further information, please call us free on 0800 652 4050

CLARION SERVICES

In Memory Driver

Download Centre:

Newsletter Subscription