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.

(more…)

Ideally your first step should be to validate the Data Definition Files (DDF’s) in your database.

(more…)

The 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.

(more…)

Building 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.

(more…)

This happens if you do not have the MS SQL Server \binn directory or the Btrieve\bin directories in your path. We need both those libraries to make the connection. IF it is not found, then we cannot continue and hence the buttons are greyed out.