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

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

Postby bfletcher » Tue 29 Aug 2006 07:03

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.
bfletcher
 
Posts: 4
Joined: Tue 29 Aug 2006 06:55

Postby Alexey » Tue 29 Aug 2006 08:26

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.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby bfletcher » Tue 29 Aug 2006 23:04

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...
bfletcher
 
Posts: 4
Joined: Tue 29 Aug 2006 06:55

Postby Alexey » Wed 30 Aug 2006 06:36

Please describe in detail what steps you perform and when exactly the license error occurs.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby bfletcher » Wed 30 Aug 2006 07:10

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)
bfletcher
 
Posts: 4
Joined: Tue 29 Aug 2006 06:55

Postby Alexey » Thu 31 Aug 2006 07:57

We found the problem and now fixing it. Look forward to the next build.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Guest » Fri 01 Sep 2006 02:12

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?
Guest
 

Postby Alexey » Fri 01 Sep 2006 06:18

Hopefully, in the beginning of the next week.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby dgoodes » Mon 18 Sep 2006 02:13

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
dgoodes
 
Posts: 1
Joined: Mon 18 Sep 2006 02:11

Postby Alexey » Tue 19 Sep 2006 08:43

We are going to issue a new build by the end of the week.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby bfletcher » Fri 22 Sep 2006 06:02

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.
bfletcher
 
Posts: 4
Joined: Tue 29 Aug 2006 06:55

Postby Alexey » Fri 22 Sep 2006 10:28

MS SQL Server integration support is scheduled to the next major version of MySQLDirect. We will consider getting this option enabled in it.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

SSIS and licensing error

Postby crcaldwell » Wed 01 Aug 2007 03:48

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
crcaldwell
 
Posts: 1
Joined: Wed 01 Aug 2007 03:39

Postby Alexey » Wed 01 Aug 2007 06:36

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.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

SSIS and licensing error

Postby zc » Tue 14 Aug 2007 22:00

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.
zc
 
Posts: 2
Joined: Tue 14 Aug 2007 21:53

Next

Return to dotConnect for MySQL