locked
migrate mainframe db2 data into sql server RRS feed

  • Question

  • I need to migrate a mainframe based DB2 system into SQL Server using SSIS.  I'm new to both SQL Server and SSIS.  Any direction you can provide would be greatly appreciated!
    Thursday, January 7, 2010 7:35 PM

Answers

  • Get yourself a DB2 OLE DB provider.  Either the Microsoft one or another vendor's.  Then, your work will be pretty simple, depending on the number of tables to migrate.  All you would need is a data flow per table, with an OLE DB Source and an OLE DB Destination component.  (More components if you need to do any data cleansing/modifications.)


    Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer
    Thursday, January 7, 2010 7:56 PM

All replies

  • Get yourself a DB2 OLE DB provider.  Either the Microsoft one or another vendor's.  Then, your work will be pretty simple, depending on the number of tables to migrate.  All you would need is a data flow per table, with an OLE DB Source and an OLE DB Destination component.  (More components if you need to do any data cleansing/modifications.)


    Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer
    Thursday, January 7, 2010 7:56 PM
  • I am not sure what you want to do here ,you want to transfer particalar tables or entire database of DB2 .Generally in SSIS we use import and export wizard for this.In that you have to choose data source name as DB2 .

    Hope this will help.
    Thursday, January 7, 2010 8:02 PM
  • I am not sure what you want to do here ,you want to transfer particalar tables or entire database of DB2 .Generally in SSIS we use import and export wizard for this.In that you have to choose data source name as DB2 .

    Hope this will help.

    Well, *generally* I avoid the Import/Export wizard because it isn't flexible enough for most of the things I do.  FWIW.


    Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer
    Thursday, January 7, 2010 8:08 PM
  • The only thing that I would add to Phil's initial response is that I would personally create a package per table, instead of just a data flow per table.  Then, I'd create one extra package as a master / parent / control package to call each of the children to populate the tables.  But, that is personal preference.  Using a single package to load multiple tables is perfectly acceptable in most environments.

    The important thing to take from this conversation is just to find a provider that allows access to the particular DB2 environment in which your data is stored.  Once you get that, the rest is pretty simple.

    Please mark answered posts. Thanks for your time.
    Thursday, January 7, 2010 10:27 PM
  • Thanks, Phil.  I sincerely appreciate your time and recommendation.
    Friday, January 8, 2010 3:09 PM
  • Thank you for your time and recommendation.  It is sincerely appreciated.  It's an entire DB2 mainframe database, which consists of about 70 tables so I figured my approach would be one at a time to better isolate logical groupings of data.
    Friday, January 8, 2010 3:10 PM
  • Thanks, Eric.  I sincerely appreciate your time and recommendation.
    Friday, January 8, 2010 3:11 PM