MySQL DataController: Difference between revisions
Moved page from wikipedia |
m automatic correction by IA |
||
| Line 26: | Line 26: | ||
The '''MySQL Datacontroller''' storage engine for the [[MySQL]] [[relational database management system]] is a storage engine which allows a user to create a table that is a local representation of a foreign (remote) table. | The '''MySQL Datacontroller''' storage engine for the [[MySQL]] [[relational database management system]] is a storage engine which allows a user to create a table that is a local representation of a foreign (remote) table. | ||
The foreign table can be located | The foreign table can be located in another storage engine like Oracle or Microsoft SQL Server (MSSQL). | ||
It utilizes the MySQL client library API, Free-TDS and OCILIB as a data transport, treating the remote data source the same way other storage engines treat local data sources. | It utilizes the MySQL client library API, Free-TDS and OCILIB as a data transport, treating the remote data source the same way other storage engines treat local data sources. | ||
Each Federated table that is defined there is one .frm (data definition file containing information such as the URL of the data source). The actual data can exist on a local or remote Oracle, Microsoft SQL Server (MSSQL), or MySQL instance. | Each Federated table that is defined there is one .frm file (data definition file containing information such as the URL of the data source). The actual data can exist on a local or remote Oracle, Microsoft SQL Server (MSSQL), or MySQL instance. | ||
To create a Federated table, one has to specify a URL in the "CONNECTION" string: | To create a Federated table, one has to specify a URL in the "CONNECTION" string: | ||
| Line 47: | Line 47: | ||
scheme://user:pass@host:port/DB/schema/tablename | scheme://user:pass@host:port/DB/schema/tablename | ||
Upon creation of a DataController table, the user must ensure that the remote data source does indeed exist or an error will be issued. | Upon creation of a DataController table, the user must ensure that the remote data source does indeed exist, or an error will be issued. | ||
The DataController Storage engine was first based on the MySQL Federated Storage Engine | The DataController Storage engine was first based on the MySQL Federated Storage Engine, authored by Patrick Galbraith and [[Brian Aker]], and is currently being maintained by Patrick Galbraith and Antony Curtis. | ||
It was introduced in 2005 with MySQL 5.0. | It was introduced in 2005 with MySQL 5.0. | ||
The DataController Storage engine was introduced in 2010 by Francis Lavalliere working with MySQL 5.1, in order to facilitate | The DataController Storage engine was introduced in 2010 by Francis Lavalliere working with MySQL 5.1, in order to facilitate access to other database engines. This plugin can also help in case of data migration, or migrating data to another database engine. | ||
== External links == | == External links == | ||
| Line 60: | Line 60: | ||
[[Category:MySQL]] | [[Category:MySQL]] | ||
{{database-software-stub}} | {{database-software-stub}} | ||
Latest revision as of 06:57, 2 May 2026
| Original author(s) | Francis Lavalliere |
|---|---|
| Initial release | 2010 |
| Engine | |
| Operating system | Linux, Mac OS X, Unix; Windows |
| Platform | x86, x86-64 |
| Available in | C/C++ |
| Type | Database engine |
| License | GNU General Public License |
| Website | http://www.acentera.com/mysql-datacontroller/ |
Search MySQL DataController on Amazon.
The MySQL Datacontroller storage engine for the MySQL relational database management system is a storage engine which allows a user to create a table that is a local representation of a foreign (remote) table. The foreign table can be located in another storage engine like Oracle or Microsoft SQL Server (MSSQL).
It utilizes the MySQL client library API, Free-TDS and OCILIB as a data transport, treating the remote data source the same way other storage engines treat local data sources. Each Federated table that is defined there is one .frm file (data definition file containing information such as the URL of the data source). The actual data can exist on a local or remote Oracle, Microsoft SQL Server (MSSQL), or MySQL instance.
To create a Federated table, one has to specify a URL in the "CONNECTION" string:
create table foo (
id int,
bar varchar(255),
dt date)
ENGINE=DATACONTROLLER CONNECTION='oracle://username:password@hostname:1521/SID/foo'
The connection URL is in the format of:
scheme://user:pass@host:port/schema/tablename
and for MSSQL where schema is dbo
scheme://user:pass@host:port/DB/schema/tablename
Upon creation of a DataController table, the user must ensure that the remote data source does indeed exist, or an error will be issued.
The DataController Storage engine was first based on the MySQL Federated Storage Engine, authored by Patrick Galbraith and Brian Aker, and is currently being maintained by Patrick Galbraith and Antony Curtis. It was introduced in 2005 with MySQL 5.0.
The DataController Storage engine was introduced in 2010 by Francis Lavalliere working with MySQL 5.1, in order to facilitate access to other database engines. This plugin can also help in case of data migration, or migrating data to another database engine.
External links
- MySQL Documentation on Federated Storage Engine
- MySQL DataController Plugin
- MySQL DataController Blog and Video demo
 | This database software-related article is a stub. You can help EverybodyWiki by expanding it. |
fr:DataController fr:Migration
This article "MySQL DataController" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:MySQL DataController. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
