Software Directory
Our Network
Top Download Titles
|
|
|
|
Data Manager for Btrieve and Pervasive SQL Enterprise
|
Data Manager for Btrieve and Pervasive SQL
Configurable data management for export, reporting, merge, rebuild,and recover.
Enterprise Edition Data Management Features
Wouldnt it be great to have a Btrieve tool that runs right out of the box against any version of Btrieve files? No need to configure ODBC drivers. No need to worry about what version of the data file or DDF files. Even create the DDF files if you need them. What if it could also drive any portion of any Btrieve data file to any database or file format on the planet? And be able to configure those exports and save them so that you could repeat it reliably over and over again?
That product is the Data Manager for Btrieve and Pervasive SQL Enterprise. Our goal was to create a tool that allowed someone to drive data from any version (new or old) of any Btrieve or Pervasive SQL data file into any other database or text file on the planet. Run right out of the box, not require any ODBC or other middleware product to read the data and do it at lightning speed. And to provide configurable export that can be saved to run over and over again to export data for reporting, integration or database conversions. So even if you are doing a one time export you can test it out, save it and reliably run the same export over and over again.
A database database export can be set up in just a couple of minutes. You can do everything from one single application. Create a DDF, Browse and/or edit your DDF and data, set up filters, export or create an export configuration. The Data Manager does not use ODBC to read the Btrieve database files. It will export data to Microsoft Access, SQL Server, Any ODBC DSN, OLE DB Providers and any fixed or delimited text files. And because it uses native access for reading the Btrieve data files it can work with any version of Btrieve or Pervasive data file new or old. And it can read that data faster than anything else available anywhere. All of the complexities of the Btrieve side are taken care of. You just have to decide where you want your data to go.
The Data Manager for Btrieve and Pervasive SQL Enterprise combines everything from the Standard edition with the added ability to configure and save exports to any database or file format.
High Performance exports and a special Super Fast Load into SQL Server
The data manager has a number features for performance tuning. And it has a special super fast load into SQL Server databases. This can increase performance over a standard load by an order of magnitude (10-20x). See Performance in the help file for details on how to set up this option.
The Configurable Data Management Tool is so Easy to Use
The configurable data management is so easy to use. And we are going to prove it to you right here through a set of screen captures. Basically you start by opening up a Btrieve Data Dictionary (DDF). This sets up default settings for each column in the grid. By default it exports all of the data to a set of tab delimited files. One for each Btrieve or Pervasive table. If that is what you need to do then select/deselect the tables you want to export and you are done. You can then run it or save it for later use. Export Configurations can be saved in either encrypted or plain text files. There are three ways you can edit the configuration grid:
1) Directly edit the configuration grid. For special columns the grid has built in pick lists and pop up forms for configuring individual cells.
2) Select Options from the view menu. With this you can perform mass changes to every cell in selected columns. This allows you to make mass changes without having to edit every column/row in the configuration grid. Very useful and time saving if you have lots of tables to export.
3) Under the tools menu select the Configuration Wizard. This wizard sets up a configuration for an individual table. Select the table row in the configuration grid and then tools/configuration wizard from the menu. The first form has common table configuration attributes and a setting for the target. The setting for the target (database, text file...) determines the next configuration forms to complete the configuration with the wizard. At most there are three forms required for a database configuration.
|
|
|
|
