|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: 2 days ago @ 12:42 PM
Points: 171,
Visits: 694
|
|
Try to create a SSIS package to insert data from SQL to Mysql. The setup is as follows OLE DB connection to SQL db ADO.net connection to Mysql. Both works fine I can select from the MYSQL db using the connection manager. I have setup a step to gather the data from SQL and dump it to a temp table. Trying to insert it to the MYSQL destination is the problem. The problem I face is that when I try and select my destination table (mysql) I can’t get a list of tables via ado.net destination workflow connection. ‘No tables or views could be loaded’. How do I select the table I want to insert into in MYSQL using SSIS.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 3,164,
Visits: 4,344
|
|
Have you installed the MySQL OLEDB provider on the machine where the SSIS package is to be run?
____________________________________________ Space, the final frontier? not any more... All limits henceforth are self-imposed. “libera tute vulgaris ex”
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: 2 days ago @ 12:42 PM
Points: 171,
Visits: 694
|
|
No I used the ODBC version. I just read that I need my source to also use ADO.Net.
http://dbperf.wordpress.com/2010/07/23/sql-server-integration-services-2008-ssis-and-mysql/
When I try to map the MYSQL table I have to create one everytime, even when I do create one. I can never remap it again. So I don't see how this package could ever run as an hourly task id this solution only used as a 1 off.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 3,164,
Visits: 4,344
|
|
I would propose using the OLE DB provider version. It is reusable, i.e. the connection could then be made using an OLE DB destination, with the provider as the relevant MySQL Data provider. All destination tables et al are then visible and available for selection and mapping. The package can then be scheduled for regular execution.
____________________________________________ Space, the final frontier? not any more... All limits henceforth are self-imposed. “libera tute vulgaris ex”
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: 2 days ago @ 12:42 PM
Points: 171,
Visits: 694
|
|
Thanks I will try that, I do need all destination tables to be visable.
Again Thanks.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: 2 days ago @ 12:42 PM
Points: 171,
Visits: 694
|
|
Is this available for SQL 2008 as I can't get the connection to work.
When I type in servername,username and password. the initial catalog is greyed out.
Using VS 2008.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: 2 days ago @ 12:42 PM
Points: 171,
Visits: 694
|
|
Almost there by following
http://www.packtpub.com/article/mysql-data-transfer-using-sql-server-integration-services-ssis
I can get the data to MYSQL but in have to create a table when creating the SSIS package. It doesn't recognise any of the existing MYsql tables and will not populate them in a drop box.
I want to transfer data to an existing table is it possible?
|
|
|
|
|
UDP Broadcaster
      
Group: General Forum Members
Last Login: Monday, June 10, 2013 4:11 AM
Points: 1,474,
Visits: 2,344
|
|
| Is it an option to change your data access method to 'SQL command' rather than 'Table or View', and write the insert statement yourself?
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: 2 days ago @ 12:42 PM
Points: 171,
Visits: 694
|
|
| Not for the destination table, has to be a table or view.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 3,164,
Visits: 4,344
|
|
Are you using an OLE DB destination component? One of the options therein is "SQL Command"
____________________________________________ Space, the final frontier? not any more... All limits henceforth are self-imposed. “libera tute vulgaris ex”
|
|
|
|