dbms: direct-access and sql file types

©1985-2006 All rights reserved. U.S. 1.800.423.1394 International +1.505.338.4188 Tech Support +1.505.345.5021 [email protected] www.basis.com

DBMS: Direct-Access andSQL File Types

Nico Spence, Chief Marketing Officer Nick Decker, Engineering Supervisor

BASIS International Ltd.

mailto:[email protected]

http://www.basis.com/

2©1985-2006 All rights reserved. U.S. 1.800.423.1394 International +1.505.338.4188 Tech Support +1.505.345.5021 [email protected] www.basis.com

Overview

► BASIS DBMS• Direct-result-set navigation and maintenance• SQL-result-set navigation and maintenance

► New DBMS Objects• BBjFileInfo• BBjOpenFileInfo

► IOLISTS vs. Templates► Extended File Types► DBMS Deployment Options




New DBMS Objects

► BBjFileInfo Object• Provides object-oriented way to access file information

traditionally retrieved from the FID() and FIN()• Associated with an open channel, so it provides a dynamic

view of the file (methods always return current information)• Retrieve information such as

Filename Filesize Filetype Key information Record information




BBjFileInfo Demonstration




BBjOpenFileInfo

► Programmatic access to opened file information• Advisory Locking• Extracted• File name• Locked• Open Type• Read Only• User• ID String• Host Name• Force Close• Documentation Link



http://www.basis.com/onlinedocs/documentation/gridctrl2/bbjfileinfo.htm


BBjOpenFileInfoDemonstration




Extracted Record Demonstration




IOLISTS

► IOLISTs - legacy style of input with drawbacks• Code using IOLISTs is less legible and more difficult

to maintain0100 IOLIST A$,B[ALL],C$,D,IOL=200

0200 IOLIST E$,F,G$

• IOLISTs are significantly slower than string templates




String Templates

► String templates – modern input style with advantages• Describes a record in a file or SQL result set

Field name Data type (character, numeric, etc.) Fixed or variable length Terminators, padding characters




String Templates

► String templates (continued) • Easy access to fields• Required for SQL and SELECT verb access• Significantly faster than IOLISTs• Code is more legible and easier to maintain• Can be retrieved via

SQL GET TABLE INFO Text area in VKEYED File




Extended File Types

► XKEYED files ► JKEYED files► VKEYED files► ESQL Files




XKEYED File Type

► BBj offers more file types• XKEYED files

Unlimited number of keys Unlimited number of key segments Unlimited key length Smaller than MKEYED files Faster record iteration




XKEYED Demonstration




JKEYED File Type

► BBj offers more file types (continued)

• JKEYED Files (Journaled Files) All file modifications are:

♦ Atomic – all operations completely succeed or completely fail

♦ Logged to automatically restore a potentially corrupt file to its last known good state




JKEYED File Type


• JKEYED Files (Journaled Files) Transaction Tracking

♦ Allows the programmer to define a set of operations on multiple files to be treated as a single operation

♦ Allows programmer to commit or rollback the entire operation




JKEYED File Type


• JKEYED Files (Journaled Files) True variable length records

♦ Perfect for BLOBs (Binary Large Objects) to store- Images- Audio- Video- Complete documents




VKEYED File Type


• VKEYED Files True variable length records

♦ Reduced disk usage♦ Perfect for BLOBs (Binary Large Objects) to store

- Images- Audio- Video- Complete documents




VKEYED File Type


• VKEYED Files (continued)

Dynamic keys - add, remove, and change keys Named keys - reduce maintenance coding Text area - write string templates in the header




VKEYED File Type


• VKEYED Files (continued)

REM Create a VKEYED fileREM 64 is the expected average record size

erase p_file$,err=*next

vkeyed p_file$,[1:1:6],[2:1:3],[3:1:2:"D"],0,64




VKEYED Details Demonstration




BBjFileInfo

► BBjFileInfo Object (continued)

Special VKEYED functionality Add keys Remove keys Change existing keys Set key names Set associated text




BASIS DBMS – New File Types




VKEYED File Size Demonstration




VKEYED File Speed Consideration

► Disk Speed► Network Speed► File structure► Differences measured in milliseconds






• ESQL Files Exclusively for SQL access; not a BBj file Created via SQL ‘Create Table’ syntax

♦ Configured in the Database Properties section of the Enterprise Manager






• ESQL File Features Contains dictionary information in the file Supports variable length records Supports dynamic index creation Offers true SQL data types

♦ Numeric values with a precision and scale♦ Dates & Timestamps

- Stored as a native type- No longer require mapping to a column extension






• ESQL File Features (continued)

Optimizations♦ Performance gains

- Faster inserts- Faster data retrieval

♦ Able to read a single column instead of always reading a whole row- No longer byte array based






• ESQL File Features (continued)

Future enhancement possibilities include ♦ Identity columns (auto increment)♦ Column and row constraints

- Foreign key relations- Not NULL constraint- Default values

♦ Optional Case-Sensitivity♦ Support for advanced ALTER TABLE syntax




ESQL Demonstration




BBj File Type Comparisons

BBj File

Maximum Keys

Maximum Key Size

Maximum File Size

Random Access

Highly Recoverable

Variable Length Records

Dynamic Key Chains

SQL Only Journaled

Indexed 0 N/A 2GB xSerial 0 N/A 2GB xDirect/Sort 1 64 2GB xMKeyed 16 120 2GB xMKeyed:Recoverable 16 120 2GB x xMKeyed:4GB 16 120 4GB xMKeyed:4GB:Recoverable 16 120 4GB x xMKeyed:64bit 16 120 Unlimited xMKeyed:64bit:Recoverable 16 120 Unlimited x xXKeyed Unlimited Unlimited 2GB xXKeyed:Recoverable Unlimited Unlimited 2GB x xXKeyed:4GB Unlimited Unlimited 4GB xXKeyed:4GB:Recoverable Unlimited Unlimited 4GB x xXKeyed:64bit Unlimited Unlimited Unlimited xXKeyed:64bit:Recoverable Unlimited Unlimited Unlimited x xJKeyed Unlimited Unlimited Unlimited x x xVKeyed (64bit & Recoverable) Unlimited Unlimited Unlimited x x x xESQL N/A N/A Unlimited x x x x x

If backwards compatibility with PRO/5 is required, BASIS recommends using MKeyed:64bit:Recoverable filesIf backwards compatibility with PRO/5 is not required, BASIS recommends using VKeyed


DBMS Deployment Options

► Single-tier• Thin Client • Interpreter • DBMS

► Two-tier• Fat Client on different machines• DMS on separate machine

► Three-tier• Thin Client on different machines and the Interpreters running on the

same machine with the DBMS• Thin Client of different machines connecting to a centralized

interpreter server that connects to a separate DBMS server


DBMS RedundantDeployment Options

► Load-balanced interpreter servers connecting to:• Storage area network SAN connected to RAID

• High-availability servers

• Highly Recoverable File System

• Journaled File System


Summary

► BASIS DBMS• Direct-result-set navigation and maintenance• SQL-result-set navigation and maintenance

► New DBMS Objects• BBjFileInfo• BBjOpenFileInfo

► IOLISTS vs. Templates► Extended File Types► DBMS Deployment Options

dbms: direct-access and sql file types

Documents

tech support

different machinesdms

centralized interpreter

storage area network