Question:
Is it reasonable to create one data flow task per table in SSIS, or is there another automated solution for moving data from ODBC to MSSQL?
Detail:
I need to convert a database that has around 750 tables from ODBC to Microsoft SQL Server 2012. I already have the schema created in SQL Server, and it is a one-on-one mapping table column. The SSIS Import wizard does not allow automatic package creation for a subset of tables, because of an exception (argument out of range) that occurs in the ODBC driver. All search results for the exception result in using a custom query (select * from table) on each of the failed tables; this works just fine, however is not feasible on a table-by-table basis.
Tables that are successful in the Wizard default CHARACTER type columns to WSTR (NVARCHAR). The target schema uses STR (VARCHAR). When using SSDT to create a data flow task, the data type defaults to STR. Changing the default to STR would be great.
The ODBC hosted database is Progress OpenEdge 10.1C. Progress provides tools for converting to Microsoft SQL Server, however when the database size is very large (8GB) the operation's length increases unreasonably exponentially (days) on powerful physical hardware. As an alternative to hosting the database through ODBC, Progress also provides flat file exports by table.
Is it reasonable to create one data flow task per table in SSIS, or is there another automated solution for moving data from ODBC to MSSQL?
Detail:
I need to convert a database that has around 750 tables from ODBC to Microsoft SQL Server 2012. I already have the schema created in SQL Server, and it is a one-on-one mapping table column. The SSIS Import wizard does not allow automatic package creation for a subset of tables, because of an exception (argument out of range) that occurs in the ODBC driver. All search results for the exception result in using a custom query (select * from table) on each of the failed tables; this works just fine, however is not feasible on a table-by-table basis.
Tables that are successful in the Wizard default CHARACTER type columns to WSTR (NVARCHAR). The target schema uses STR (VARCHAR). When using SSDT to create a data flow task, the data type defaults to STR. Changing the default to STR would be great.
The ODBC hosted database is Progress OpenEdge 10.1C. Progress provides tools for converting to Microsoft SQL Server, however when the database size is very large (8GB) the operation's length increases unreasonably exponentially (days) on powerful physical hardware. As an alternative to hosting the database through ODBC, Progress also provides flat file exports by table.