Page 1 of 2

Trial License & SQL Server 2005 Import (SSIS) or DTS

Posted: Tue 29 Aug 2006 07:03
by bfletcher
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.

Posted: Tue 29 Aug 2006 08:26
by Alexey
You have to install MySQLDirect .NET on target machine. Note that according to License Agreement you may install MySQLDirect .NET on target machine only in minimal configuration.

Posted: Tue 29 Aug 2006 23:04
by bfletcher
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...

Posted: Wed 30 Aug 2006 06:36
by Alexey
Please describe in detail what steps you perform and when exactly the license error occurs.

Posted: Wed 30 Aug 2006 07:10
by bfletcher
Alexey wrote:Please describe in detail what steps you perform and when exactly the license error occurs.
1. Installed MySQLDirect.NET on MS SQL Server 2005 box
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)

Posted: Thu 31 Aug 2006 07:57
by Alexey
We found the problem and now fixing it. Look forward to the next build.

Posted: Fri 01 Sep 2006 02:12
by Guest
Alexey wrote:We found the problem and now fixing it. Look forward to the next build.
Ok Great. Any idea when the next build will be available?

Posted: Fri 01 Sep 2006 06:18
by Alexey
Hopefully, in the beginning of the next week.

Posted: Mon 18 Sep 2006 02:13
by dgoodes
Hi,

Just following up on this, wondering if you have an ETA on the next build of MySQLDirect .NET Driver? The web page still shows version 3.50.

Thanks
Dan

Posted: Tue 19 Sep 2006 08:43
by Alexey
We are going to issue a new build by the end of the week.

Posted: Fri 22 Sep 2006 06:02
by bfletcher
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.

Posted: Fri 22 Sep 2006 10:28
by Alexey
MS SQL Server integration support is scheduled to the next major version of MySQLDirect. We will consider getting this option enabled in it.

SSIS and licensing error

Posted: Wed 01 Aug 2007 03:48
by crcaldwell
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

Posted: Wed 01 Aug 2007 06:36
by Alexey
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.

SSIS and licensing error

Posted: Tue 14 Aug 2007 22:00
by zc
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.