I need to select some data from WX2 Database and put it in MYSQL DB.
Can any one help me on this?
Is ODBC.ini configuration will work for the mysql database to connect to WX2 database?
Thanks
To access the data in Kognitio you could use the ODBC driver to retrieve it, or for better performance use the bulk unloader utilities to export it as CSV, which you could then load into MySQL.
If you were going the other way round, pulling data FROM MySQL TO Kognitio, you could bulk unload as CSV from MySQL then bulk load into Kognitio, or you could use the External Table functionality of version 8 to access MySQL tables on demand from Kognitio via an ODBC connector.
The documentation covers off all these approaches.
Related
I have a MySQL file that I would like to explore using sqltool. I do not want to deploy a MySQL database because I only need to run a few queries on the data; I do not need persistence.
I understand that sqltool will allow me to create an in-memory database and run queries on it. This is perfect for my use-case, but how do I make it accept the MySQL dialect of SQL?
Additionally, is the process the same for other dialects such as Postgres SQL?
You need to deploy a MySQL database.
The HSQLDB SqlTool allows you to connect to a MySQL server using the MySQL JDBC driver, or to any other database server such as PostgreSQL using the relevant JDBC driver.
The SqlTool also allows you to create an in-memory database when used with HSQLDB, but this type of database is different from a MySQL database.
I have a MySQL database contains large amount of data.
I wanted to write a C# service program to migrate that data into SQL Server database.(Service should work fine with Insert as well as update with out performance issue).
Please help us if there is a way to accomplish this. If there is another way to achieve this is also fine. But, the MySQL client is not present in the local machine. But we could access the database from the server.
You can use the import and export functions in sqlserver, after installing a odbc mysql
Currently experiencing an issue whereby I am exporting a MySQL structure and data from a server into a sql file, ready for importing into a local database.
When importing the sql file into a local database, numerous records are changing dramatically. The columns in question tend to be of type bit(1).
The local setup uses the following versions Apache 2.2.17, PHP 5.3.5 and MySQL 5.5.8.
The server is currently using MySQL 5.1.56.
Any ideas what can be done to rectify this scenario?
Try using the --hex-blob parameter with the mysqldump utility when obtaining the sql dump.
I have database in MySQL V5. I wants to import and export data to MySQL using File Maker pro 11 without creating any file.i.e. I want direct connection between File Maker and MySQL.
Please help me......
I can highly recommend the Open Source Databases ODBC driver from Actual Technologies. It's a Mac OS X ODBC driver that I've used it on multiple occasions to connect FileMaker to a MySQL database. With it you can create a "shadow table" that actually shows data from the MySQL database and import from a FileMaker table to a MySQL table using the standard script steps for import and export. This is the ESS that Sam was speaking of. For the Windows equivalent, see FileMaker's list of ODBC drivers.
We have a JDBC Plugin for that. You can do a SELECT query on your MySQL DB, then loop over the returned rows and read values out. It also supports dumping the SELECT to a txt file, which you can then import.
For importing into MySQL, your best bet is to do INSERT/UPDATE queries.
Also, you might consider using ESS, which is FileMaker's built-in way of talking to MySQL.
That's about it. I can always just dump it to csv and read it in, but I was hoping to avoid that.
Since both Interbase and MySql have ODBC drivers, how about using your favorite development environment to write an app that opens each table in the IB database and copies it into the MySql database? There are various languages and IDE's that support data access using odbc.
This would be nicer than using csv because your code could copy the schema during the process of copying each table.
You can use Database Workbench
Cross database development
Use the Schema Compare and Migration
Tools to compare testing and deployed
databases, migrate existing databases
to different database systems.
ps: I don't know why you want to migrate from Interbase to MySQL but you can also take a look to Firebird