Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →How to create TaxJar federated tables in MySQL
Use the SQL Gateway and the ODBC Driver to set up federated tables for TaxJar data in MySQL .
You can use the SQL Gateway to configure a MySQL remoting service and set up federated tables for TaxJar data. The service is a daemon process that provides a MySQL interface to the CData ODBC Driver for TaxJar: 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 TaxJar data just as you would local MySQL tables.
Connect to TaxJar 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.
To authenticate to the TaxJar API, you will need to first obtain the API Key from the TaxJar UI.
NOTE: the API is available only for Professional and Premium TaxJar plans.
If you already have a Professional or Premium plan you can find the API Key by logging in the TaxJar UI and navigating to Account -> TaxJar API. After obtaining the API Key, you can set it in the APIKey connection property.
Additional Notes
- By default, the CData connector will retrieve data of the last 3 months in cases where the entity support date range filtering. You can set StartDate to specify the minimum creation date of the data retrieved.
- If the API Key has been created for a sandbox API account please set UseSandbox to true, but not all endpoints will work as expected. For more information, refer to the TaxJar developer documentation.
Configure the SQL Gateway
See the SQL Gateway Overview to set up connectivity to TaxJar 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 TaxJar 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 TaxJar. 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 fedTaxJar FOREIGN DATA WRAPPER mysql OPTIONS (USER 'sql_gateway_user', PASSWORD 'sql_gateway_passwd', HOST 'sql_gateway_host', PORT ####, DATABASE 'CData TaxJar 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 ( ..., transactionid TYPE(LEN), userid TYPE(LEN), ..., ) ENGINE=FEDERATED DEFAULT CHARSET=latin1 CONNECTION='fedTaxJar/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 TaxJar 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 TaxJar. Refer to the following example:
SELECT fed_orders.transactionid, local_table.custom_field FROM local_table JOIN fed_orders ON local_table.foreign_transactionid = fed_orders.transactionid;