SSIS Data Migration from Progress DB to SQL Server 2005

Question

SSIS Data Migration from Progress DB to SQL Server 2005

sureshj

Valued Member

Points: 74
More actions
January 7, 2008 at 2:28 pm

#177901

Hi,
I am trying to create a DTS package in SQL Server 2005 to migrate data from our Progress DB to SQL Server. For some reason when I choose .NET ODBC driver I am not able to look at the schema and data information of the Progress DB.
This is the first time i am trying to create a DTS to migrate data from Progress to SQL 2005. Any help will be greatly appreciated.
Thanks
suresh

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Dan Colbert-387424 SSCrazy Points: 2195 More actions · Answer 1

None of the native ODBC drivers will work with Progress. You need to contact Progress to get one.

When you do, be prepared to deal with data type mismatches and overflows. Progress doesn't strongly type any data types in the data. They are only "suggestions". I've dealt with an implementation of Progress to MSSQL Server where we had a bunch of overflows because what was "defined" as a char(20) had 3000 characters.

Hope this helps!

Dan

sureshj Valued Member Points: 74 More actions · Answer 2

Hi Daniel,

Thanks a lot for your suggestions. Just another quick question. What driver did you use for doing the data migration. If you can tell me the name of the ODBC driver and the version that would really be helpful. We are currently have Data Direct and Meraint ODBC drivers. But both of them are not getting recognized when I try to create a SSIS package. Any help on this would be greatly appreciated.

Thanks

suresh

Dan Colbert-387424 SSCrazy Points: 2195 More actions · Answer 3

You should be able to get the ODBC driver from Progress. Install it on whatever machine(s) the SSIS packages will run.

If you are running on Windows 64bit, you'll need to reference it as 32bit for it to work.

Everything gets pulled back as nvarchar(3000) due to the data typing funkiness I mentioned in my last post.

Dan

Stefan K SSCommitted Points: 1786 More actions · Answer 4

Hi,

heres a pretty good website about available ODBC connections for SQL Server http://ssis.wik.is

If you do not get it to work using OLEDB/ODBC drivers and so on a possible workaround could be to export the data to flat files using database tools of progress and then import all the stuff to SQL Server. If you have tons of data this is the fastest solution anyway, regarding the load time.

Good luck!

Kindest Regards,

SK