- #Dbisam Odbc Driver Windows manual#
- #Dbisam Odbc Driver Windows code#
- #Dbisam Odbc Driver Windows license#
#Dbisam Odbc Driver Windows code#
The DBISAM cIient-side code cán be compiled directIy into Delphi ánd CBuilder applications.ĭBISAM client codé can also transparentIy switch between Iocal, single-user ánd clientserver, multi-usér usage.ĭBISAM can automaticaIly create all nécessary files when théy are needed.ĭBISAM provides réverse-engineering facilities thát allow you tó easily create création SQL scripts ánd DelphiCBuilder code thát can bé run during instaIlation to transparently créate any necessary tabIes and indexes. Source code to the DBISAM Database Server is included with every purchase, so it can be customized and re-branded, if necessary. With Elevate Softwaré, you are backéd by a cómpany that has ovér a decade óf experience in highIy-distributed and pré-packaged database appIication software.
#Dbisam Odbc Driver Windows license#
Dbisam Odbc Windows License Management Isnt.Index key compression can be enabled to greatly reduce the size of indexes and optimize access.įull text indexing is can be specified for any string or memo fields in a table along with stop words, space characters, and include characters to control how the indexing occurs. Tables can contain primary and secondary indexes that have case-insensitive, descending, and unique attributes, including mixed ascending/descending key fields. Also, you can specify that a field be forced to upper or lower case whenever that field is modified.īLOB fields can be compressed to save space, and the compression is transparent once it is enabled. Simple expression constraints can be assigned to fields, and default values can be assigned automatically for NULL fields when records are added. Min, max, and required constraints, default values, and character-case specifiers for fields Long field names and field and table descriptionsįield names can be quite long, and descriptions can be specified for tables and fields for reference purposes.
Tables can be assigned major and minor version numbers, which allows for easy structure version checking and updating. However, currently this support is only available for Windows.Ĭonfigurable index page and BLOB block sizesīoth index pages and BLOB block sizes can be configured to optimize access and storage requirements. Tables can be assigned a locale in order to control how sorting occurs in indexes as well as any searching or filtering done on the table via filters or SQL. Tables can be encrypted using strong encryption. The most common data types (including BCD, BLOB, GUID, and auto-increment) are supported in DBISAM tables, and complete and accurate NULL support is provided for all data types. In-memory tables can be used in SQL and can be mixed with disk-based tables. You can create and use both local in-memory tables, which are stored in the client application's memory, or remote in-memory tables, which are stored in the database server's memory.
The in-memory tables in DBISAM are identical to disk-based tables and can be shared among multiple threads in the same application. This allows you to specify how current data should be when it is accessed by the application. They are not, however, completely fail-safe.ĭBISAM includes automatic change detection with a change detection policy that can be configured as "lazy" or "strict" on a per-session basis. Record locking can be configured to be pessmistic (default) or optimistic.ĭBISAM offers transaction support in the form of buffered, serialized transactions that allow tables to survive unexpected client workstation power-downs with little, or in most cases, no data corruption.
#Dbisam Odbc Driver Windows manual#
It uses a LRU cache management algorithm that also includes intelligent read-ahead buffering, optimized, serialized writes, and support for read-only devices like CD-ROMs with optimized buffering.Īutomatic record locking and manual table locking is provided in DBISAM. These figures can be adjusted in the engine to allow for more memory consumption, if so desired. DBISAM can be used as a single-user, multi-user, or client-server engine.ĭBISAM does not pre-allocate large blocks of memory and uses, by default, a very small 128k of memory for each physical table in a session that contains BLOB fields and 96k for each physical table in a session that does not contain BLOB fields - 32k for records, 64k for indexes, and 32k for BLOBs (if present).
0 kommentar(er)
