A common cause of unsatisfactory post-migration performance can usually be traced to the index files. To enjoy speedy performance of your Btrieve program it is necessary to create proper index files. BTR2SQL may have failed to create indexes for a number of reasons. The two most common are duplicate data and running out of disk space.
Why is my Btrieve program so slow after a migration?
February 19th, 2009What is a good first step before I migrate from Btrieve?
February 19th, 2009Ideally your first step should be to validate the Data Definition Files (DDF’s) in your database.
What do I have to do to migrate data?
February 19th, 2009The data migration process occurs in two simple steps:
1. Creation of a table with the same name and file structure as the Btrieve file.
2. Copying of records from the Btrieve file to the table.
How to validate DDFs using the DDF Validator tool
February 19th, 2009Building DDFs for your Btrieve database can be the largest undertaking of a migation project. Without DDFs, your data will be read as a conglomeration of meaningless bytes. Validating DDF’s is a listed prerequisite rather than an optional step that you will need to perform before migration.
Reasons a Magic eDeveloper App Can’t be Multi-DBMS
February 20th, 2008Magic eDeveloper advertises multi-dbms support through “gateways”. You design the app once and simply configure the backend gateway to one of many. However, if the application is designed for ISAM (Btrieve), then getting it to run against a SQL backend has many challenges.