Recreate DDF's for table in Pervasive Database

I have a Pervasive database for Sage BusinessVision ERP where I have created some additional tables. In the folder the tables/files for the BusinessVision ERP are with extension btr and the tables I created manually are with extension mkd.

After an upgrade of the ERP and adding the new DDF's from Sage my manually created tables no longer show in the pervasive control center.

What I can I do with the DDF files so that the manually created tables will show again in the control center?

I'm using MS SQL SSIS to pull data from the manually created tables
Who is Participating?
Bill BachPresidentCommented:
Not wirh the native tools that Sage installs. Another solution would be to restore the DDFs from your old system to a different folder, create a new database for them, move the MKD files into the same folder, and then access them with cross-database joins.

A cross database join simply indicates the new dbname, like this:
   SELECT * FROM NewDB.MyTable;

If you use aliases in your queries, then you should be able to make this change very easily by just changing the table names in each query to include the new database name. With this solution, you'll never need to worry about this issue again!
The best solution would be to rerun the original CREATE TABLE statements but add the IN DICTIONARY clause so that only the table entry is created.
Bill BachPresidentCommented:
You will need to log into the new database (with the new DDF's) and re-run your original CREATE statements.  I recommend doing this with these steps:
- Get all users out of the system.
- Rename the MKD files so that they are out of the way.
- Run the CREATE TABLE statements to create the files you need.  This will recreate the MKD files, but they will all be empty.
- Optional: If there is ANY chance that you messed this up, do a BUTIL -STAT on the new MKD file and compare it to the BUTIL -STAT on the old MKD file.  The keys should match (except for record counts, of course).  If they do not match, DROP TABLE and do it again until it matches.
- Copy the old MKD files on top of the new ones. This will put your data back into the location where the database engine wants it.

You can also try to do this with CREATE TABLE..IN DICTIONARY, but this can sometimes give you bad results, and I don't recommend it.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

GerhardpetAuthor Commented:
The problem is that I don't have the CREATE TABLE statements. The tables were created a long time ago. Is there anyway to access the mkd files for the CREATE TABLE SQL statements?
GerhardpetAuthor Commented:
We can't find the old DDF's so we are out of luck.

Thanks for your help solution is your solution so I will award points to you.
Bill BachPresidentCommented:
Do you not have any backups from before the upgrade?  I always save at least one or two year-end backups, just in case.
GerhardpetAuthor Commented:
Yes we do have backups from at least 2 years ago but the DDF's are not there with these additional tables.

The tables were created about 5-6 years and have not been used for at least 3 years.

It would be nice to get the data but it is not the end of the world
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.