How to create EnterpriseDB federated tables in MySQL

You can use the SQL Gateway to configure a MySQL remoting service and set up federated tables for EnterpriseDB data. The service is a daemon process that provides a MySQL interface to the CData ODBC Driver for EnterpriseDB: After you have started the service, you can create a server and tables using the FEDERATED Storage Engine in MySQL. You can then work with EnterpriseDB data just as you would local MySQL tables.

Connect to EnterpriseDB Data

If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.

The following connection properties are required in order to connect to data.

• Server: The host name or IP of the server hosting the EnterpriseDB database.
• Port: The port of the server hosting the EnterpriseDB database.

You can also optionally set the following:

• Database: The default database to connect to when connecting to the EnterpriseDB Server. If this is not set, the user's default database will be used.

Connect Using Standard Authentication

To authenticate using standard authentication, set the following:

• User: The user which will be used to authenticate with the EnterpriseDB server.
• Password: The password which will be used to authenticate with the EnterpriseDB server.

Connect Using SSL Authentication

You can leverage SSL authentication to connect to EnterpriseDB data via a secure session. Configure the following connection properties to connect to data:

• SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
• SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
• SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
• SSLClientCertType: The certificate type of the client store.
• SSLServerCert: The certificate to be accepted from the server.

Configure the SQL Gateway

See the SQL Gateway Overview to set up connectivity to EnterpriseDB data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.

Create a FEDERATED Server and Tables for EnterpriseDB Data

After you have configured and started the service, create a FEDERATED server to simplify the process of creating FEDERATED tables:

Create a FEDERATED Server

The following statement will create a FEDERATED server based on the ODBC Driver for EnterpriseDB. Note that the username and password of the FEDERATED server must match a user account you defined on the Users tab of the SQL Gateway.

CREATE SERVER fedEnterpriseDB
FOREIGN DATA WRAPPER mysql
OPTIONS (USER 'sql_gateway_user', PASSWORD 'sql_gateway_passwd', HOST 'sql_gateway_host', PORT ####, DATABASE 'CData EnterpriseDB Sys');

Create a FEDERATED Table

To create a FEDERATED table using our newly created server, use the CONNECTION keyword and pass the name of the FEDERATED server and the remote table (Orders). Refer to the following template for the statement to create a FEDERATED table:

CREATE TABLE fed_orders (
  ...,
  shipname  TYPE(LEN),
  shipcity  TYPE(LEN),
  ...,
)
ENGINE=FEDERATED
DEFAULT CHARSET=latin1
CONNECTION='fedEnterpriseDB/orders';

NOTE: The table schema for the FEDERATED table must match the remote table schema exactly. You can always connect directly to the MySQL remoting service using any MySQL client and run a SHOW CREATE TABLE query to get the table schema.

Execute Queries

You can now execute queries to the EnterpriseDB FEDERATED tables from any tool that can connect to MySQL, which is particularly useful if you need to JOIN data from a local table with data from EnterpriseDB. Refer to the following example:

SELECT 
  fed_orders.shipname, 
  local_table.custom_field 
FROM 
  local_table 
JOIN 
  fed_orders 
ON 
  local_table.foreign_shipname = fed_orders.shipname;