Why is my Btrieve program so slow after a migration?

Following a Btrieve to SQL migration, 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.

For example, a Btrieve table might contain dates such as 12/12/99 and 12/12/1999 in two separate records. Since BTR2SQL converts all dates to four-digits during migration, this data will cause a unique constraint violation if the date field is part of an index.

Solution: Index Maintenance Utilitiy

The Index Maintenance Utility is designed to quickly test the indexes to verify that each file was created properly. We strongly recommend that you take a few moments to run the Index Maintenance utility after every conversion.

With BTR2SQL active you can press F1 to activate and use the Help system to obtain up todate instructions surrounding the Index Maintenance Utility.

Please note: For this option to work properly you will need to locate the Btrieve files that you will be working with and verify that they are present as the utility will be comparing the database structures of the files.