My Question is the following how to convert .sql
mysql to postgresql sql , so I can uploaded to postgresql database at heroku
and please let it be free tool.
many thanks
Here are two tools for migrating from MySQL, both are actively maintained:
1) pgloader https://github.com/dimitri/pgloader. With it, conversion is just a one line:
pgloader mysql://user#localhost/dbname_in_mysql postgresql:///dbname_in_postgres
2) pg_chameleon https://pypi.python.org/pypi/pg_chameleon – this one is actually a replication system so it's suitable for systems under load.
Related
So i have a low of dmp files that were to make tables in my sql developer database is there a way I could use those same dump files for my mysql database tables?
I never did that, but Googling around I found out that there are tools that make it possible. T
OraDump-to-MySQL is a program to export data from Oracle dump files into MySQL, MariaDB or Percona database. The program does direct reading from the dump, so Oracle installation is not required. Command line support allows to script, automate and schedule the conversion process.
I'm not posting a link (so that someone wouldn't call it spamming); I guess you'll be able to find it yourself.
I have a Mysql database backup dump file (.sql), and I want to migrate this file directly into Oracle by using sqldeveloper. Will this work?
It won't work. If you do it manually from a dump, you would have to do a lot of data conversion, modify the create table code to work for oracle and so on. It would be a lot of work.
But if you have SQL Developer, it apparently has a process to do precisely that.
Check out that link:
http://www.oracle.com/technetwork/database/migration/mysql-093223.html
I hope that helps.
It cannot be realized in automatic mode, due to different basic syntax of Oracle and MySQL dump files. In addition, Orqcle uses its own RMAN utility for controlling backups and restoration.
A most viable solution is to write a script converting MySQL dump file into the format recognizable by Oracle. I guess these procedures can exist in Internet, available for (free?) downloading.
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.
Caveat: I have zero experience with MySQL.
I've been given a series of files to do a data conversion and would like to migrate the provided data into SQL Server 2008. The files are:
*.myd
*.myi
*.frm
These file types, as I understand it, are MyISAM. I believe that if I had a running MySQL instance, migrating to SQL Server would be fairly straightforward. I could could either use SQL Server's import wizard or Microsoft SQL Server Migration Assistant for MySQL v1.0. Unfortunately, these files are what I'm stuck with -- I just don't have access to the original MySQL instance.
I also don't presently have MySQL as a running instance locally and I'm not sure if there would be compatibility issues with the files I have.
Can I attach them to MySQL 5.5 with the goal of performing a SQLDump or perhaps to use either tool mentioned above? Am I missing a better way?
Yes, you can easily attach them to MySQL 5.5. Then you can dump the tables using mysqldump (be aware that you will need to either modify dump and remove mysql-specific stuff from the dump, or probably customize mysqldump output - check mysqldump documentation for details). You can also try to link Mysql instance to SQL Server, and then copy tables using SELECT ... INTO [sql_server_table_name] FROM [mysql_table_name].
In any case, the hardest part is to migrate stored procedures/triggers. Mysql and SQL Server have quite a different syntax for them, so you probably cannot automate this process.
Update
Also, I forgot to mention that you will have to modify mysql auto_increment columns to IDENTITY([next_auto_increment_value],1) SQL server.
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