Friday, October 19, 2012

SQL Server: Extracting Data from OpenEdge Progress without OLE DB Driver

Importing data from OpenEdge’s Progress® data base is simple if you have OLE DB data provider. But if you don’t have OLE DB driver or unable to configure it properly then there are few simple steps to migrate data from OpenEdge’s Progress® to SQL Server.
(Worst thing in Progress ® database I found that you can only restore your database from backup file with only version with which this backup files was created i.e. you can’t restore Progress 9.1 backup file on Progress 10 or newer version)
We will achieve our data migration goal through two step, first to import table structures and import data from flat files to newly created tables.
Copying Table Structuer:
Once you have restored your required backup file, you can access it from “Data Administrator” by connecting your database file.
 Progress normally keep its databases with extension “db” at installation drive\Progress\WRK\YourDatabaseName.db
Once you are connected to your desired database, click on “ProgressDB to M SQL Server” through given path.
Provide necessary information for ProgressDB to ODBC Conversion. Type any name of your choice for “Name of schema holder database” and correct ODBC data source name.

On pressing OK button, it will create “.sql” file on “installation drive\Progress\WRK\”. This sql file contains create table query for all database tables. Open this .sql file in SQL Server and create tables.

Extracting Data
In next step we will extract table data to CSV files.
Select table of your choice.
 Provide file name with target folder path. Select “All (Max 255)” fields to export. You can provide WHERE clause to filter output rows. Press OK button to proced
 Provide any record start string. It will add given string at start of each row. Which you can remove, once data is imported in SQL Server.
 Now you have tables structure and data in text format. Execute simple Data Import process to import your desired data from text files to already created tables.

No comments:

Post a Comment