1. DataFlex Connectivity Kit for Pervasive.SQL Eddy Kleinjan

2. Agenda  The Big Picture  Pervasive.SQL models  Driver Concepts  WebApp Demo

3. Where Does It Fit in? The Pervasive.SQL Database DataFlex Connectivity Kit for Pervasive.SQL

4. Fast & Reliable  Client/Server Architecture Spreads Load  Server Caching Improves Transaction  Automatic Crash Recovery  Transactions (Concurrent & Exclusive)  24h Operations through On-Line Backups and Transaction Logs  Zero Administration

5. Great Match!  Server Platforms  Windows NT  Novell NetWare  Client Platforms  Dos, 16-bin Windows, 32-bit Windows

6. Pervasive.SQL Models

7. Using Pervasive.SQL 7 Tools  Setup Utility to Set Parameters  Use InstallScout for Client Setup  Monitor Utility Watches Activity  Use Pervasive.SQL ODBC  Use DDF Ease to manage your data

8. Driver Design Goals  Compatibility with DataFlex  Easy To Use Migration Tools  Automatic Data Restructuring  Connect to Existing Btrieve Data  Data Sharing Through DDF’s

9. As Compatible as possible  No Program Changes  No Database Changes  No Data Dictionary Changes  Supports Original Recnum Value  Supports Record- and Filelocking  Filelocking prevents deadlock situations!  Supports Overlap fields

10. Easy Conversion  DataFlex to Pervasive.SQL  Support in all versions of Visual DataFlex  Character Mode utility provided  Migrate ‘DataFlex for Btrieve’ Data using New Migration Utility  Integrated in VDF6  Separate ‘Database Builder’ Utility

11. To Recnum Or Not To Recnum  Recnum is numeric record identifier  Driver Has It’s Own Record  Indexes Don’t Have to be Unique  Only Required When Original Recnum Values needs to be Retained

12. Automatic Restructuring  Use ‘Database Builder’  Use DataFlex Database API  Add, Change and Remove Fields  Add, Change and Remove Indexes

13. Btrieve is Recordmanager  Doesn’t know about fieldtypes  Doesn’t check data  Only uses types for Sorting

14. DataFlex File Structure Byte 0 : Header : Fields : Indexes : Other Byte 512 : Data End-of-File

15. Btrieve File Structure : File : Fields : Indexes : Other : Data

16. DDF’s  Data Definition Files  Describe a File’s Structure  File information (FILE.DDF)  Field information (FIELD.DDF)  Index information (INDEX.DDF)

17. Pervasive.SQL Models

18. Data Sharing  DDF’s are the way to share data  Pervasive’s ODBC driver uses DDF’s  Crystal Reports uses DDF’s  Most Btrieve Based Products use DDF’s

19. INT Files  Contains Extra Information  DataFlex Field Types (Overlap)  Relationship Information  Converted with/without Recnum support  Overrule DDF settings

20. Connect to Btrieve Data  Include DDF Directory in DFPath  Create Filelist entry to DDF  “DFBTRDRV:MyFile”  Create INT File  “MyFile.INT”  Supports non-unique indexes

21. DDF Ease  Utility to create/maintain database  ‘Check Database’ Tests SQL Compatibility  ‘Check Database’ Function Reports:  Overlap fields (No SQL Equivalent)  Text/Binary fields > 255 char while not being the last field in the record

22. Other features  Use Password Security  Allow read-only access  Control Transaction type at runtime  File- or Recordlocking  New ‘open as’ mechanism

23. Version 1.2 Improvements  Structure Caching  Faster Finding (up to 30%)  ‘Runtime Server’ support  Zerofile can do ‘Re-create’ instead of ‘Record-by-Record’ delete  New Fields: Currency, Timestamp and 64-bit integers

24. Version 1.2 Improvements  Improved Deadlock Detection  Supports alternate ‘Open As’  Open “DFBTRDRV:path|DDFName” as x  DFBTRDRV: Drivername  Path: path to file (e.g. CUSTBACK.BTR)  DDFName: Name of ‘as’ file

25. Structure Caching : File : Fields : Indexes : Data Writes DDF Into to CCH FileNext Open Read CCHImproves File Open SpeedCCH Expires on Changes

26. Structure Caching  Writes DDF info to Sequential file (CCH)  Next Open Read CCH instead of DDF  Improves File Opening Speed up to 400% Depending on Configuration  CCH File Automatically Expires On Structure Changes

27. Faster Findings  Record ID must be read for each record  Previous Version Used Database Call  New Version Gets ID from Memory

28. Runtime Server Support  Special 1-user NetWare Version  Allows 1 NetWare User but Unlimited Process Users  Low-Cost Database Server

29. Zerofile Improvements  Current Version deletes Record-by- Record  New Version can be Configured To Recreate File  Single-User Operation  Much faster on Large Datafiles

30. Pervasive.SQL 2000  SQL Interface supports multiple Text/Binary field larger than 255 bytes  Server, Workgroup and Workstation  Internet Data Server (IDS)

31. Demo  Converting Data using  Migrating ‘DataFlex for Btrieve’  WebApp: ‘WebDDF’

32. Questions? About Pervasive.SQL? About the Driver?

33. Thank You!