Ready to get started?

Learn more about the CData ODBC Driver for Act CRM or download a free trial:

Download Now

Connect to Act CRM Data as a Federated Tables in MySQL

Use the SQL Gateway and the ODBC Driver to set up federated tables for Act CRM data in MySQL .

You can use the SQL Gateway to configure a MySQL remoting service and set up federated tables for Act CRM data. The service is a daemon process that provides a MySQL interface to the CData ODBC Driver for Act CRM: 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 Act CRM data just as you would local MySQL tables.

Connect to Act CRM 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 User and Password properties, under the Authentication section, must be set to valid Act! user credentials. In addition to the authentication values, see the following:

  • Connecting to Act! Premium

    In addition to the authentication values, the URL to Act! is also required; for example https://eup1-iis-04.eu.hosted.act.com/.

    Additionally, you must specify the ActDatabase you will connect to. This is found by going to the About Act! Premium menu of your account, at the top right of the page, in the ? menu. Use the Database Name in the window that appears.

  • Connecting to Act! Premium Cloud

    To connect to your Act! Premium Cloud account, you also need to specify the ActCloudName property. This property is found in the URL address of the Cloud account; for example https://eup1-iis-04.eu.hosted.act.com/ActCloudName/.

Note that retrieving ActCRM metadata can be expensive. It is advised that you set the CacheMetadata property to store the metadata locally.

Configure the SQL Gateway

See the SQL Gateway Overview to set up connectivity to Act CRM 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 Act CRM 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 Act CRM. 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 fedActCRM
FOREIGN DATA WRAPPER mysql
OPTIONS (USER 'sql_gateway_user', PASSWORD 'sql_gateway_passwd', HOST 'sql_gateway_host', PORT ####, DATABASE 'CData ActCRM 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 (Activities). Refer to the following template for the statement to create a FEDERATED table:

CREATE TABLE fed_activities (
  ...,
  activitydisplayname  TYPE(LEN),
  subject  TYPE(LEN),
  ...,
)
ENGINE=FEDERATED
DEFAULT CHARSET=latin1
CONNECTION='fedActCRM/activities';

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 Act CRM 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 Act CRM. Refer to the following example:

SELECT 
  fed_activities.activitydisplayname, 
  local_table.custom_field 
FROM 
  local_table 
JOIN 
  fed_activities 
ON 
  local_table.foreign_activitydisplayname = fed_activities.activitydisplayname;