DBISAM
DBISAM is the standard for replacing the BDE in Delphi or C++Builder applications. It has has been deployed to thousands of locations around the world, and can be branded so that no one even knows that DBISAM is being used. It is licensed per-developer, and includes royalty-free distribution. License management isn't required at all, and the money that you used to pay to the database engine vendor is now your profit to keep.
Overview
DBISAM compiles directly into your application with no external libraries required. Runtime package support is also provided if so desired. It has a very small footprint and does not require any forms support in Delphi 6 and C++Builder 6 and higher, which helps keep the size of non-UI applications like services or web applications to a minimum.
DBISAM is available for Delphi, C++Builder, Borland Developer Studio, CodeGear RAD Studio, and Embarcadero RAD Studio. Для просмотра ссылки Войдиили Зарегистрируйся, Для просмотра ссылки Войди или Зарегистрируйся, Для просмотра ссылки Войди или Зарегистрируйся, Для просмотра ссылки Войди или Зарегистрируйся, and Для просмотра ссылки Войди или Зарегистрируйся components are provided for all of these versions of Delphi, C++Builder, Borland Developer Studio, CodeGear RAD Studio, and Embarcadero RAD Studio.
The complete source code for all utilities provided, and source code for DBISAM itself is available for an additional charge.
The utilities provided with DBISAM are:
Engine Features
DBISAM can be used as a Для просмотра ссылки Войдиили Зарегистрируйся
DBISAM 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). These figures can be adjusted in the engine to allow for more memory consumption, if so desired. Для просмотра ссылки Войдиили Зарегистрируйся that also includes intelligent read-ahead buffering, optimized, serialized writes, and support for read-only devices like CD-ROMs with optimized buffering.
Automatic Для просмотра ссылки Войдиили Зарегистрируйся is provided in DBISAM. Record locking can be configured to be pessmistic (default) or optimistic.
DBISAM offers transaction support in the form of Для просмотра ссылки Войдиили Зарегистрируйся that allow tables to survive unexpected client workstation power-downs with little, or in most cases, no data corruption. They are not, however, completely fail-safe.
DBISAM includes Для просмотра ссылки Войдиили Зарегистрируйся with a change detection policy that can be configured as "lazy" or "strict" on a per-session basis. This allows you to specify how current data should be when it is accessed by the application.
The Для просмотра ссылки Войдиили Зарегистрируйся in DBISAM are identical to disk-based tables and can be shared among multiple threads in the same application. 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. In-memory tables can be used in SQL and can be mixed with disk-based tables.
DBISAM supports Для просмотра ссылки Войдиили Зарегистрируйся on a single table or query result set, with complete reconciliation control during application of the cached updates in order to handle possible errors. DBISAM also includes IProvider support that makes it ideal for use with the standard TClientDataSet component.
The DBISAM engine, represented by the Для просмотра ссылки Войдиили Зарегистрируйся component, is highly Для просмотра ссылки Войди или Зарегистрируйся. Triggers, server-side procedures, scheduled events, custom SQL and filter functions, and custom engine signatures can be added and modified via the engine. However, server-side procedures and scheduled events are only available when the engine is Для просмотра ссылки Войди или Зарегистрируйся as a database server. Triggers allow you to add code that is executed before or after any insert, update, or delete. Custom SQL and filter functions can be used to add complex functions to the SQL and filter grammar, thus enabling you to reduce the complexity of your SQL and filter expressions. Custom engine signatures can be used to "sign" all tables, streams, backups, and remote database server request and responses with a unique stamp so that only your application can access these resources.
Table Format Features
The default maximum file size in DBISAM is Для просмотра ссылки Войдиили Зарегистрируйся. DBISAM uses up to Для просмотра ссылки Войди или Зарегистрируйся. All free space in DBISAM tables is automatically recycled. In addition, any free space can be removed from a table immediately by Для просмотра ссылки Войди или Зарегистрируйся the table. DBISAM uses fixed-length record sizes and variable index page and BLOB block sizes. When Для просмотра ссылки Войди или Зарегистрируйся, some of the most useful feature include:
SQL and Filter Support
DBISAM includes a Для просмотра ссылки Войдиили Зарегистрируйся, including a query optimizer, query plans, live and canned result sets, parameterized queries, query progress events, scripts, and extended SQL syntax for DBISAM-specific features.
Client-Server Access
DBISAM includes support for Для просмотра ссылки Войдиили Зарегистрируйся to a DBISAM database server. You can switch between local or multi-user usage and client-server usage with just a Для просмотра ссылки Войди или Зарегистрируйся. Remote sessions include support for keep-alive pinging or the ability to maintain sessions that can survive connection interruptions, complete with dead session management for sessions that will never be reconnected due to a fatal client problem. Connection timeouts for remote sessions can be adjusted, and an event is fired whenever DBISAM is about to disconnect a remote session due to inactivity.
© Для просмотра ссылки Войдиили Зарегистрируйся
Для просмотра ссылки Войдиили Зарегистрируйся
DBISAM is the standard for replacing the BDE in Delphi or C++Builder applications. It has has been deployed to thousands of locations around the world, and can be branded so that no one even knows that DBISAM is being used. It is licensed per-developer, and includes royalty-free distribution. License management isn't required at all, and the money that you used to pay to the database engine vendor is now your profit to keep.
Overview
DBISAM compiles directly into your application with no external libraries required. Runtime package support is also provided if so desired. It has a very small footprint and does not require any forms support in Delphi 6 and C++Builder 6 and higher, which helps keep the size of non-UI applications like services or web applications to a minimum.
DBISAM is available for Delphi, C++Builder, Borland Developer Studio, CodeGear RAD Studio, and Embarcadero RAD Studio. Для просмотра ссылки Войди
The complete source code for all utilities provided, and source code for DBISAM itself is available for an additional charge.
The utilities provided with DBISAM are:
Utility | Description |
Database System Utility | This utility allows the developer or end user to create, browse, update, restructure, search, query, and print DBISAM tables from a convenient and easy-to-use interface. |
Server Administration Utility | This utility allows the developer or end user to administer a DBISAM database server from a convenient and easy-to-use interface. This utility can modify server configuration data, users, databases, and user rights as well as retrieve server log information. All functions are subject to having administrator rights on the database server being administered and access can be controlled on a per-user basis. |
Engine Features
DBISAM can be used as a Для просмотра ссылки Войди
DBISAM 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). These figures can be adjusted in the engine to allow for more memory consumption, if so desired. Для просмотра ссылки Войди
Automatic Для просмотра ссылки Войди
DBISAM offers transaction support in the form of Для просмотра ссылки Войди
DBISAM includes Для просмотра ссылки Войди
The Для просмотра ссылки Войди
DBISAM supports Для просмотра ссылки Войди
The DBISAM engine, represented by the Для просмотра ссылки Войди
Table Format Features
The default maximum file size in DBISAM is Для просмотра ссылки Войди
Table Feature | Description |
Data types | The most common Для просмотра ссылки Войди |
Encryption | Tables can be encrypted using Для просмотра ссылки Войди |
International locales | 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. However, currently this support is only available for Windows only. |
Configurable index page and BLOB block sizes | Both index pages and BLOB block sizes can be configured to optimize access and storage requirements. |
User-defined versioning | Tables can be assigned major and minor version numbers, which allows for easy structure version checking and updating. |
Long field names and field and table descriptions | Field names can be quite Для просмотра ссылки Войди |
Min, max, and required constraints, default values, and character-case specifiers for fields | Simple expression constraints can be assigned to fields, and default values can be assigned automatically for NULL fields when records are added. Also, you can specify that a field be forced to upper or lower case whenever that field is modified. |
BLOB compression | BLOB fields can be compressed to save space, and the Для просмотра ссылки Войди |
Primary and secondary indexes | Tables can contain primary and secondary indexes that have case-insensitive, descending, and unique attributes, including mixed ascending/descending key fields. |
Configurable index key compression | Для просмотра ссылки Войди |
Full text indexing | Full 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. |
SQL and Filter Support
DBISAM includes a Для просмотра ссылки Войди
Client-Server Access
DBISAM includes support for Для просмотра ссылки Войди
© Для просмотра ссылки Войди
Для просмотра ссылки Войди