MySQL Workbench 5.2.47

MySQL Workbench 6.0 – A Sneak Preview

akojima — Wed, 22 May 2013 12:30:57 +0000

The MySQL Workbench team has been a little quiet for the past few months, but that’s because we’ve been busy working on an exciting new version. Read more about it in Tomas’ blog

MySQL Workbench team hiring C++ and/or Python developers

akojima — Mon, 08 Apr 2013 14:14:57 +0000

The MySQL Developer Tools team at Oracle is looking for good C++ and/or Python developers to help with the MySQL Workbench project.

In the Workbench team, you’ll be responsible for developing features, maintaining the existing codebase and interact with the community to improve the project.

We’re looking for candidates to work from office at Guadalajara, Mexico or from home in Romania, Ukraine, Portugal, Poland or Czech Republic, with availability to start in the team in late May.

Job Description

Software Developer, MySQL Workbench

Software Development position responsible for development and maintenance
of Python and/or C++ code for the MySQL Workbench product.

Requirements

* 5+ years experience developing solid Python or C/C++ code
* Experience developing desktop GUI applications
* Good knowledge of the C/C++ language
* MySQL database development and administration

* Experience with one or more of the GUI platforms we use (gtkmm, Cocoa, .NET/Winforms) a plus

About the company

Oracle, the world’s premier database company, is hiring expert engineering staff for MySQL
- the world’s most popular open source database because of its consistent fast performance,
high reliability and ease of use. MySQL engineering organization is highly technical team
spread across different geographies and strive for excellence and high quality in day-to-day work processes.

To apply, search for MySQL Workbench in
http://irecruitment.oracle.com

Installing a driver for Microsoft SQL Server and Sybase ASE in Linux and Mac

Sergio de la Cruz — Mon, 18 Feb 2013 22:30:36 +0000

In a recent post we showed you how to migrate a SQL Server database to MySQL. There, we used the oficial Microsoft ODBC driver and that’s OK if you are running MySQL Workbench in Windows. But what if your desktop OS is some Linux variant or Mac OS X?

It turns out that Microsoft has recently released an ODBC driver for Linux. However, you can’t use this driver with MySQL Workbench for Linux. (Actually you can, but you would have to rebuild Workbench). The main reason is that this ODBC driver was linked against unixODBC (an ODBC driver manager), while Workbench uses another ODBC driver manager: iODBC and the two of them can’t coexist in the same system.

So for Linux and Mac we prefer to go in a different direction and use FreeTDS, an alternate ODBC driver for Microsoft SQL Server. As a bonus, the very same driver can be used for connecting to Sybase Adaptive Server Enterprise, an RDBMS also supported in the MySQL Workbench Migration Wizard.

In spite that you can find FreeTDS in the software repositories of several modern Linux distributions, you are encouraged to download it and compile it yourself. Most distros provide fairly old FreeTDS versions and virtually all of them come linked against unixODBC, which is not supported by Workbench. Fortunately, the process for compiling and installing it is pretty straightforward. Here are the steps you should follow:

Go to the FreeTDS homepage and download a recent version of the driver’s source code. Make sure that you have at least version 0.92. We advise you to use the latest stable version rather than a nightly snapshot. Save this tarball in a directory where you have write permissions (something like /home//freetds would do).
If you are in Linux, make sure that you have installed the essential build tools (C/C++ compiler, linker, etc.) and the development files for iODBC. Try running this from the command line if your are using a Debian based distro like Ubuntu:
```
$> sudo apt-get install build-essential libiodbc2-dev
```
If your distro uses rpm packages (Red Hat, Fedora, etc.) the command would be like this:
```
$> su -
$> yum install make automake gcc gcc-c++ libiodbc-devel
```
Mac users can skip this step since the apropriate development files are already included in their system.
Since there are a couple of options you would have to pass to the driver’s configure script, we have created a script file to help you pass this with no pain. You can find this script file in /usr/share/mysql-workbench/extras/build_freetds.sh if you are in Linux or inMySQLWorkbench.app/Contents/SharedSupport/build_freetds.sh if you use a Mac. Locate this helper script and copy it to the same directory where you put the driver’s tarball.
Now it’s the time to actually build the driver. If you are not already there, cd to the directory where you put the helper script and run the helper script from there:
```
$> ./build_freetds.sh
```
Wait until the compilation finishes.
Now that the driver is built, you should proceed to install it by running make install as root. And there you go, you should have the FreeTDS driver installed inside the /usr/lib or the /usr/local/lib directory. It will be named libtdsodbc.so.
Proceed to register the installed FreeTDS driver as explained here.

Now you should be ready to use the driver to migrate Microsoft SQL Server and Sybase ASE databases to MySQL using the MySQL Workbench Migration Wizard.

MySQL Workbench 5.2.47 released

akojima — Fri, 15 Feb 2013 18:44:40 +0000

The MySQL developer tools team announces the availability of version 5.2.47
of the MySQL Workbench GUI tool. This is a minor maintenance release, addressing a problem during data copy in databases with triggers, during migrations and server upgrades.

For a full list of issues fixed in this release, see the release notes.

Please get your copy from our Downloads site. In Windows, you can also
use the MySQL Windows Installer to update Workbench and other MySQL products.

Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

Workbench Documentation can be found here.

Utilities Documentation can be found here.

If you need any additional info or help please get in touch with us.

Post in our forums or leave comments on our blog pages.

- The MySQL Workbench Team

MySQL Workbench 5.2.46 released

akojima — Tue, 05 Feb 2013 13:34:26 +0000

The MySQL developer tools team announces the availability of version 5.2.46
of the MySQL Workbench GUI tool. This version contains 30 resolved bugs
and support for the new MySQL 5.6 server.

Additionally, MySQL Utilities 1.2.0 have been included on the distribution.

For a full list of issues fixed in this release, see the release notes.

Please get your copy from our Downloads site. In Windows, you can also
use the MySQL Windows Installer to update Workbench and other MySQL products.

Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

Workbench Documentation can be found here.

Utilities Documentation can be found here.

If you need any additional info or help please get in touch with us.

Post in our forums or leave comments on our blog pages.

- The MySQL Workbench Team

MySQL Workbench 5.2.45 GA Released

juanram — Fri, 28 Dec 2012 01:21:33 +0000

The MySQL developer tools team announces the availability of version 5.2.45 of the MySQL Workbench GUI tool. This version contains various fixes and minor enhancements and includes 72 resolved bugs.

This version contains the following significant updates:
- Support for several new MySQL 5.6 features
- Import recordsets from CSV file for the Inserts editor in Modeling and in the SQL Editor
- Improved trigger editor
- more

Additionally, MySQL Utilities 1.1.1 have been included on the distribution.

For a full list of issues fixed in this release, see http://dev.mysql.com/doc/relnotes/workbench/en/wb-news-5-2-45.html

Please get your copy from our Downloads site. In Windows, you can also use the MySQL Windows Installer to update Workbench and other MySQL products.

Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

Utilities Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/mysql-utilities.html

If you need any additional info or help please get in touch with us.

Post in our forums or leave comments on our blog pages.

- The MySQL Workbench Team

How-To: Migrate PostgreSQL databases to MySQL using the MySQL Workbench Migration Wizard

Sergio de la Cruz — Wed, 21 Nov 2012 14:06:30 +0000

MySQL Workbench 5.2.41 introduced the new Migration Wizard module. This module allows you to easily and quickly migrate databases from various RDBMS products to MySQL. As of Workbench 5.2.44 you can migrate databases from Microsoft SQL Server, PostgreSQL and Sybase Adaptive Server Enterprise. It also provides for generic migrations, i.e. migrations from other RDBMSes that are not explicitely supported, provided that they have a well behaved ODBC driver. More on this in an upcoming post…

Additionally, you can use the Migration Wizard to perform MySQL to MySQL database migrations, which can be used for tasks such as copying a database across servers or migrating data across different versions of MySQL.

We have already described in a previous post how to use the Migration Wizard to migrate a Microsoft SQL Server database to MySQL. In this post we are going to migrate a PostgreSQL database to MySQL using the Migration Wizard.

So lets get our hands dirty and run through the Migration Wizard in order to migrate a PostgreSQL database to MySQL. In the rest of this post I assume that you have:

A running PostgreSQL instance in which you have proper access to the database you want to migrate. (I’ll call this database from now on the source database). I have a PostgreSQL instance running in a computer (an Ubuntu 12.04 box) in my local network. I have installed on top of it the Pagila Sample Database from pgFoundry. I’m using the standard postgres user, which has full privileges. You can use whatever PostgreSQL version you have at hand, but keep in mind that the Migration Wizard officially supports PostgreSQL 8.0 and newer so older PostgreSQL versions might not work.
A running MySQL Server instance with proper user access. The Migration Wizard supports MySQL versions from 5.0 onwards so make sure you have a supported version. For this tutorial I’m using MySQL Server 5.5.27 CE installed in the very same Ubuntu PC where PostgreSQL is running.
MySQL Workbench 5.2.44 or newer. This time I’m going to use Workbench for Linux. I have Workbench running in another computer with Ubuntu 12.10 installed.

Lets start now…

Download, compile (Linux and Mac only) and install a PostgreSQL ODBC driver

You need to install an ODBC driver for PostgreSQL in the machine where you installed MySQL Workbench. Please follow the instructions here.

Open MySQL Workbench and start the Migration Wizard

From the main MySQL Workbench screen you can start the Migration Wizard by clicking on the Database Migration launcher in the Workbench Central panel or through Database > Migrate in the main menu.

A new tab showing the Overview page of the Migration Wizard should appear.

Read carefully the Prerequisites section. You can read there that you need an ODBC driver for your source RDBMS installed. If you have installed the psqlODBC driver as explained in the previous section, you are good to go.

Set up the parameters to connect to your source database

Click on the Start Migration button in the Overview page to advance to the Source Selection page. In this page you need to provide the information about the RDBMS you are migrating, the ODBC driver to use and the parameters for the connection. The name of the ODBC driver is the one you set up when you registered your psqlODBC driver with the driver manager (psqlODBC, for example).

If you open the Database System combo box youll find a list of the supported RDBMSes. Select PostgreSQL from the list. Just below it theres another combo box named Stored Connection. It will list saved connection settings for that RDBMS. You can save connections by marking the checkbox at the bottom of the page and giving them a name of your preference.

The next combo box is for the selection of the Connection Method . This time we are going to select ODBC (manually entered parameters) from the list since we are going to manually type the parameters for our PostgreSQL connection. Other alternatives are ODBC data sources and ODBC connection strings.

Now its the time for putting the parameters for your connection. In the Driver text field, type the ODBC driver name from the previous step (psqlODBC). Fill the remaining parameters (Hostname, Port, Username, Password and Database) with the appropriate values. The psqlODBC driver does not allow to connect without specifying a database name, so make sure you put the name of your database before attempting to connect. At this point you should have something like this:

Click on the Test Connection button to check the connection to your PostgreSQL instance. If you put the right parameters you should see a message reporting a successful connection attempt.

Set up the parameters to connect to your target database

Click on the Next button to move to the Target Selection page. Once there set the parameters to connect to your MySQL Server instance. When you are done click on the Test Connection button and verify that you can successfully connect to it.

Select the schema(ta) to migrate

Click on the Next button to move to the next page. The Migration Wizard will communicate to your PostgreSQL instance to fetch a list of the schemata in your source database.

Verify that all tasks have successfully finished and click on the Next button to move forward. You will be given a list of schemata to select the ones to migrate. The Schema Selection page will look like this:

Select the Pagila sample database from the list and its default schema public. Now look at the options below. A PostgreSQL database is comprised of one catalog and one or more schemata. MySQL only supports one schema in each database (to be more precise, a MySQL database is a schema) so we have to tell the Migration Wizard how to handle the migration of schemata in our source database. We can either keep all of the schemata as they are (the Migration Wizard will create one database per schema), or merge them into a single MySQL database. The two last options are for specifying how the merge should be done: either remove the schema names (the Migration Wizard will handle the possible name colisions thay may appear along the way) or either adding the schema name to the database object names as a prefix. Lets select the second option since we only have one schema and we are not particularly interested in keeping its meaningless public name.

Select the objects to migrate

Move to the next page using the Next button. You should see the reverse engineering of the selected schema in progress. At this point the Migration Wizard is retrieving relevant information about the involved database objects (table names, table columns, primary and foreign keys, indices, triggers, views, etc.). You will be presented a page showing the progress as shown in the image below.

It may take some time, depending on how fast is your connection to the server, your PostgreSQL server load and your local machine load. Wait for it to finish and verify that everything went well. Then move to the next page. In the Source Objects page you will have a list with the objects that were retrieved and are available for migration. It will look like this:

As you can see the Migration Wizard discovered table objects in our source database. If you click on the Show Selection button you will be given the oportunity to select exactly which of them you want to migrate as shown here:

The items in the list to the right are the ones to be migrated. Note how you can use the filter box to easily filter the list (wildcards are allowed there too). By using the arrow buttons you can filter out the objects that you dont want to migrate. At the end, dont forget to clear the filter text box to check the full list of the selected objects. We are going to migrate all of the table objects, so make sure that all of them are in the Objects to Migrate list and that the Migrate Table Objects checkbox is checked. Most of the time youll want to migrate all objects in the schema anyway, so you can just click Next.

Review the proposed migration

Move to the next page. You will see the progress of the migration there. At this point the Migration Wizard is converting the objects you selected into their equivalent objects in MySQL and creating the MySQL code needed to create them in the target server. Let it finish and move to the next page. You might have to wait a little bit before the Manual Editing page is ready but you’ll end up with something like this:

As you can see in the image above there is a combo box named View . By using it you can change the way the migrated database objects are shown. Also take a look at the Show Code and Messages button. If you click on it you can see (and edit!) the generated MySQL code that corresponds to the selected object. Furthermore, you can double click in a row in the object tree and edit the name of the target object. Suppose you want your resultant database to have another name. No problem: double click on the Pagila row and rename it.

An interesting option in the View combo box is the Column Mappings one. It will show you all of the table columns and will let you individually review and fix the mapping of column types, defalt values and other attributes.

Run the resultant MySQL code to create the database objects

Move to the Target Creation Options page. It will look like this:

As you can see there, you are given the options of running the generated code in the target RDBMS (your MySQL instance from the second step) or just dumping it into a SQL script file. Leave it as shown in the image and move to the next page. The migrated PostgreSQL code will be executed in the target MySQL server. You can view its progress in the Create Schemata page:

Once the creation of the schemata and their objects finishes you can move to the Create Target Results page. It will present you a list with the created objects and whether there were errors while creating them. Review it and make sure that everything went OK. It should look like this:

You can still edit the migration code using the code box to the right and save your changes by clicking on the Apply button. Keep in mind that you would still need to recreate the objects with the modified code in order to actually perform the changes. This is done by clicking on the Recreate Objects button. You may need to edit the generated code if its execution failed. You can then manually fix the SQL code and re-execute everything. In this tutorial we are not changing anything, so leave the code as it is and move to the Data Transfer Setup page by clicking on the Next button.

Transfer the data to the MySQL database

The next steps in the Migration Wizard are for the transference of data from the source SQL Server database into your newly created MySQL database. The Data Transfer Setup page allows you to configure this process.

There are two sets of options here. The first one allows you to perform a live transference and/or to dump the data into a batch file that you can run later. The other set of options gives you a way to tune up this process.

Leave the default values for the options in this page as shown in the above image and move to the actual data transference by jumping to the next page. It will take a little while to copy the data. At this point the corresponding progress page will look familiar:

Once it finishes, move to the next page. You will be presented a report page summarizing the whole process:

And that should be it. Click on the Finish button to close the Migration Wizard.

A little verification step

Now that the Pagila database was successfully migrated, let’s see the results. Open an SQL Editor page associated with your MySQL Server instance and query the Pagila database. You can try something like SELECT * FROM pagila.actors. You should get something like this:

Conclusions

By now you should have a pretty good idea of the capabilities of the Migration Wizard and should be ready to use it for your own migrations. The official documentation is also there for you and you can always ask any question in the comments of this post or in the migration official forum. Live long and prosper!

Set up and configure PostgreSQL ODBC drivers for the MySQL Workbench Migration Wizard

Sergio de la Cruz — Wed, 14 Nov 2012 22:22:40 +0000

If you plan to use the MySQL Workbench Migration Wizard to migrate databases from PostgreSQL to MySQL you first need to configure an ODBC driver to connect to your PostgreSQL server.

In this post I’ll cover how to set up and configure psqlODBC, the official ODBC driver for PostgreSQL.

Installing the psqlODBC Driver

The procedure is different for every platform so make sure to follow the instructions that correspond to the OS where you have MySQL Workbench installed. The driver needs to be installed in that machine, as explained in the MySQL Workbench documentation.

Windows

If you are running MySQL Workbench on Windows download the MSI package for psqlODBC. Go to its download page (http://www.postgresql.org/ftp/odbc/versions/msi/) and pick the most recent file from the list. (The most recent one is at the bottom of the page.)

Unzip the downloaded file and install the provided MSI package. This is all you have to do. You can skip the rest of this post.

Linux

The Migration Wizard uses iODBC as a driver manager for all of its ODBC connections in Linux. This may give you some troubles because most Linux distributions provide ODBC drivers compiled against unixODBC. This is another driver manager not supported by MySQL Workbench so you won’t be able to use those drivers unless you compile them against iODBC. Here’s what you should do.

Make sure that you have iODBC installed. If you are using Debian, Ubuntu or another Debian based distro, type this command in your terminal:

$> sudo apt-get install iodbc libiodbc2-dev libpq-dev libssl-dev

For RPM based distros (RedHat, Fedora, etc.) type this command instead of the previous one:

$> sudo yum install iodbc iodbc-dev libpqxx-devel openssl-devel

Now we need to install the PostgreSQL ODBC drivers.

Download the psqlODBC source tarball from here. Use the latest version available for download. As of this writing the latest version corresponds to the file psqlodbc-09.01.0200.tar.gz. Extract this tarball to a directory in your hard drive and open a terminal and cd into that directory.

Type this in the terminal window:

$> ./configure --with-iodbc --enable-pthreads
$> make
$> sudo make install

Verify that you have the file psqlodbcw.so in the /usr/local/lib directory.

Mac OS X

To build psqlODBC in Mac OS X, you need to have Xcode and the “Command Line Tools” additional component installed, so that the gcc compiler is available. You can get Xcode for free in the AppStore and install the Command Line Tools from Preferences -> Downloads.

Type this in the terminal window:

$> ./configure --with-iodbc --enable-pthreads
$> CFLAGS="-arch i386 -arch x86_64" make
$> sudo make install

Registering your ODBC Driver (Linux and Mac OSX)

Open the iODBC Data Source Administrator application either by typing iodbcadm-gtk in the command line or by launching it from the Overview page of the MySQL Workbench Migration Wizard, using the Open ODBC Administrator button. From the main MySQL Workbench screen you can start the Migration Wizard by clicking on the Database Migration launcher in the Workbench Central panel or through Database > Migrate in the main menu.

Go to the ODBC Drivers tab. You should have something like this:

Click on the Add a driver button and fill the values as shown here:

After you click OK you should have the psqlODBC driver registered.

Installing MySQL Workbench in Ubuntu 12.10

Sergio de la Cruz — Wed, 14 Nov 2012 14:55:03 +0000

Last month Ubuntu 12.10 was released and we tried to install MySQL Workbench on it. So we went to http://www.mysql.com/downloads/workbench/ and downloaded the .deb file for the most recent Workbench version (5.2.44 as of this writing). We then opened the .deb file with the Ubuntu Software Center application and tried to install it. Unfortunately the following message appeared:

Dependency is not satisfiable: libctemplate0

The problem here is that the libctemplate package provided by Ubuntu 12.10 corresponds to a higher version (libctemplate2). Installing this version instead wouldn’t work since MySQL Workbench is linked against the older one. We’ll handle this dependency issue in future releases, but here’s a workaround:

Download the previous libctemplate version from here for 32 bits or here for 64 bits.

Open the .deb file with the Ubuntu Software Center and install it. (Or just type “sudo dpkg -i libctemplate_0.97-1_i386″ from the command line.) Once this package is installed you can proceed to install and run MySQL Workbench and it should work OK.

MySQL Workbench 5.2.44 GA Released

juanram — Fri, 28 Sep 2012 01:06:11 +0000

The MySQL developer tools team announces the availability of version 5.2.44
of the MySQL Workbench GUI tool. This version contains various fixes
and minor enhancements and includes 8 resolved bugs.

This version improves the Migration Tool to support additional RDBMSes
- PostgreSQL 8.x and 9.x
- Sybase Adaptive Server Enterprise 15.x
- Any RDBMS that implements the INFORMATION_SCHEMA views from the SQL-92 standard

Additionally, MySQL Utilities 1.1.0 have been included on the distribution.

For a full list of issues fixed in this release, see http://dev.mysql.com/doc/workbench/en/changes-5.2.x.html

Please get your copy from our Downloads site. In Windows, you can also
use the MySQL Windows Installer to update Workbench.

Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

Utilities Documentation can be found here.
http://dev.mysql.com/doc/workbench/en/mysql-utilities.html

If you need any additional info or help please get in touch with us.

Post in our forums or leave comments on our blog pages.

- The MySQL Workbench Team