Trial License & SQL Server 2005 Import (SSIS) or DTS
Trial License & SQL Server 2005 Import (SSIS) or DTS
Hi All,
We want to try out the Core Lab MySQL Driver to import data from MySQL to SQL Server 2005 as a scheduled SSIS package. We want to create this via the Import Wizard in SQL Server, however it is complianing about a License not being found. How do I activate the license in this context - i.e. there is no .NET project, just want to use the driver as a Provider for SQL Server Import.
thanks.
We want to try out the Core Lab MySQL Driver to import data from MySQL to SQL Server 2005 as a scheduled SSIS package. We want to create this via the Import Wizard in SQL Server, however it is complianing about a License not being found. How do I activate the license in this context - i.e. there is no .NET project, just want to use the driver as a Provider for SQL Server Import.
thanks.
I have MySQLDirect.NET installed in minimal configuration on the SQL Server box (target machine).
So there are only two servers in the equation, the MS SQL Server and the MySQL 4.x Server.
I am using the MS SQL Server directly to create the Import Package and I get the license error. So I'm not sure what you mean by target machine as the MS SQL Server is the target machine, the MySQL 4.x Server is the Source...
So there are only two servers in the equation, the MS SQL Server and the MySQL 4.x Server.
I am using the MS SQL Server directly to create the Import Package and I get the license error. So I'm not sure what you mean by target machine as the MS SQL Server is the target machine, the MySQL 4.x Server is the Source...
1. Installed MySQLDirect.NET on MS SQL Server 2005 boxAlexey wrote:Please describe in detail what steps you perform and when exactly the license error occurs.
2. Right click on database in SQL Server Management Studio and select Tasks -> Import Data
3. Choose CoreLab MySQLDirect.NET Data Provider as Data Source
4. Fill out connection details to MySQL 4.x database
5. Click Next and error is displayed:
There operation could not be completed.
Additional Information:
License not found. Please view "Licensing" topic in MySQLDirect .NET documentation for details or contact Core Lab technical support. (CoreLab.MySql)
Good News is, the new driver gets past the license issue.
Bad News is that the "Copy data from one or more tables or views" option on the Import Data Wizard is disabled, which is the option we were really hoping this driver would enable. The only option we have is "Write a query to specify the data to transfer" which is no good as we want to import all of the tables, not just one.
Bad News is that the "Copy data from one or more tables or views" option on the Import Data Wizard is disabled, which is the option we were really hoping this driver would enable. The only option we have is "Write a query to specify the data to transfer" which is no good as we want to import all of the tables, not just one.
-
- Posts: 1
- Joined: Wed 01 Aug 2007 03:39
SSIS and licensing error
When trying to execute an ssis package I am receiving the error. License not found. Please view "Licensing" topic in MySQLDirect .NET documentation for details or contact Core Lab technical support. (CoreLab.MySql). I've tried using MySQLDirect .NET 4.0 and MySQLDirect .NET 4.2 providers and receive the error on both. I can get the provider to work correctly when debugging a package; however, when trying to schedule the package I receive the error. I am working on a clustered instance and the provider is installed on the active node.
Thanks,
Chris
Thanks,
Chris
Which process run scheduled package? I think the problem is in the way of loading our assembly. You can wrap our MySqlConnection class in your own class library where you should add licenses.config file with the name of that process (which run the package).
For more information about licensing please see "Licensing" topic of MySQLDirect .NET documentation.
For more information about licensing please see "Licensing" topic of MySQLDirect .NET documentation.
SSIS and licensing error
Chris, have you resolved this issue yet? I am experiencing the same problem when importing the SSIS package into SQL Stored Packages, MSDB and running it.