A collection of "Migrating to MySQL"

A Test Drive of the MySQL Migration Suite

by Gregory L. Magnusson

Got data in a proprietary database such as Microsoft SQL Server or Oracle 9i? The MySQL Migration Suite can help you move it to the MySQL open source database. Find out what's involved in the migration and how well the suite facilitates the transition.

FileMaker to MySQL Migration

Summary:

FileMaker is unmatched in usability thus allowing even novices to quickly create useful database applications for themselves and other users. FileMaker solutions are often developed by individuals and departments who are working independently from a corporate IT department due to cost factors or reduced IT staffing. However as the number of users grows, it may be necessary to migrate a FileMaker database solution to MySQL. MySQL offers inexpensive hosting options and greater scalability which is comparable to an Oracle database (as shown in the well known eWeek benchmarks).

This article covers the procedures involved with migrating a FileMaker 6 database running on Windows to a MySQL database running on any platform. Additional info is included regarding changes to this procedure which are required to convert FileMaker 7 to MySQL.

Full Article 

Migrating from Microsoft Access to MySQL

Introduction

Businesses that use Access eventually begin to struggle against its limitations. Now they have an alternative: Move data repositories to a system that provides better performance and reliability and that is more flexible in how it allows information to be used. MySQL provides the features you need to follow this course. MySQL includes a business strength database server that runs under either Windows, Linux, or Unix. MySQL features InnoDB, the table type that provides performance and reliability enhancements such as row-level locking, transaction support, and automatic crash recovery. By using MySQL as a data management platform, you can continue to manipulate your data through Access as a front end if you wish. But you can also exploit your data in other ways, for example, by using MySQL to help you establish or strengthen your web presence. To do this, deploy a web server that handles requests from people who visit your site and tie it to MySQL using a web programming language. A popular combination employs the Apache web server and the Perl and PHP programming languages. Perl and PHP both are extremely popular for web programming, and both interface easily with MySQL.

The following article explores reasons to consider using MySQL instead of Access for data management, and provides guidelines for transferring information out of Access and into MySQL when you're ready to make the switch.

Microsoft Access or MySQL?

Microsoft Access is a popular data management application that allows you to store information in tables that it manages directly from the local disk. You can also use Access as a front end, that is, as an interface to information that is located elsewhere and handled by another storage management system. In this case, Access acts as a client that connects to a server that provides the data. The MySQL database system is one such storage manager; if you install the MySQL Connector/ODBC driver (formerly known as MyODBC), Access can make ODBC connections to MySQL servers over the network. You can still use the contents of your tables through Access, but the tables themselves are hosted by the MySQL server.

Access has its strengths, such as an easy to use interface. Access also has its limitations--it's generally used as a personal or single-user application, typically for managing limited amounts of data. (Access is not commonly used for databases hundreds of megabytes in size, for example.) Because of its storage management limitations, you may be considering how to retain the Access interface but migrate your information to a storage manager with greater capabilities. Or you may even be considering a move away from Access entirely. This article outlines some benefits that you stand to gain by using MySQL to manage your data, and provides some guidelines to help you migrate locally stored Access tables to MySQL. The final section of the article lists links to locations where you can find the tools discussed here.

Full Article

Migrating from Microsoft SQL Server and Access to MySQL

 Introduction

One of the more common themes present on the various MySQL forums and mailing lists is that of data migration. Typically requests are made by users of Microsoft® Access and Microsoft SQL Server who are looking to migrate their data (and client applications) to a MySQL database. Developers often ask for tools that can be used to convert an Access database to MySQL (or convert an MSSQL database to MySQL), without realizing that there is more to migrating an application to MySQL than simply converting data.

In this article I will cover the basics of migrating an application from an Access or SQL Server database to MySQL. We'll start with various reasons why you should (or should not) migrate your existing Access or SQL Server database to MySQL, then cover the planning stages of an application migration. Next we will look at the tools and methods for migrating your actual data from Access/MSSQL to MySQL, followed by some general guidelines for modifying your client application from a Microsoft database to MySQL. Finally, we'll look at some considerations to make when deploying your new MySQL database and application.

Full Article