How to connect PolyBase to Jira Assets

PolyBase for SQL Server allows you to query external data by using the same Transact-SQL syntax used to query a database table. When paired with the CData ODBC Driver for Jira Assets, you get access to your Jira Assets data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live Jira Assets data using T-SQL queries.

NOTE: PolyBase is only available on SQL Server 19 and above, and only for Standard SQL Server.

The CData ODBC drivers offer unmatched performance for interacting with live Jira Assets data using PolyBase due to optimized data processing built into the driver. When you issue complex SQL queries from SQL Server to Jira Assets, the driver pushes down supported SQL operations, like filters and aggregations, directly to Jira Assets and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. And with PolyBase, you can also join SQL Server data with Jira Assets data, using a single query to pull data from distributed sources.

Connect to Jira Assets

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs. To create an external data source in SQL Server using PolyBase, configure a System DSN (CData Jira Assets Sys is created automatically).

Jira Assets supports connecting and authenticating via the APIToken.

To generate an API token:

1. Log in to your Atlassian account.
2. Navigate to Security < Create and manage API Token < Create API Token.

Atlassian generates and then displays the API token.

After you have generated the API token, set these parameters:

• AuthScheme: APIToken.
• User: The login of the authenticating user.
• APIToken: The API token you just generated.

You are now ready to connect and authenticate to Jira Assets.

Click "Test Connection" to ensure that the DSN is connected to Jira Assets properly. Navigate to the Tables tab to review the table definitions for Jira Assets.

Create an External Data Source for Jira Assets Data

After configuring the connection, you need to create a master encryption key and a credential database for the external data source.

Creating a Master Encryption Key

Execute the following SQL command to create a new master key, 'ENCRYPTION,' to encrypt the credentials for the external data source.

CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password';

Creating a Credential Database

Execute the following SQL command to create credentials for the external data source connected to Jira Assets data.

CREATE DATABASE SCOPED CREDENTIAL jiraassets_creds
WITH IDENTITY = 'username', SECRET = 'password';

Create an External Data Source for Jira Assets

Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for Jira Assets with PolyBase:

• Set the LOCATION parameter , using the DSN and credentials configured earlier.

For Jira Assets, set SERVERNAME to the URL or address for your server (e.g. 'localhost' or '127.0.0.1' for local servers; the remote URL for remote servers). Leave PORT empty. PUSHDOWN is set to ON by default, meaning the ODBC Driver can leverage server-side processing for complex queries.

CREATE EXTERNAL DATA SOURCE cdata_jiraassets_source
WITH ( 
  LOCATION = 'odbc://SERVER_URL',
  CONNECTION_OPTIONS = 'DSN=CData Jira Assets Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = jiraassets_creds
);

Create External Tables for Jira Assets

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to Jira Assets data from your SQL Server instance. The table column definitions must match those exposed by the CData ODBC Driver for Jira Assets. You can refer to the Tables tab of the DSN Configuration Wizard to see the table definition.

Sample CREATE TABLE Statement

The statement to create an external table based on a Jira Assets Objects would look similar to the following:

CREATE EXTERNAL TABLE Objects(
  ID [nvarchar](255) NULL,
  Name [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Objects',
  DATA_SOURCE=cdata_jiraassets_source
);

Having created external tables for Jira Assets in your SQL Server instance, you are now able to query local and remote data simultaneously. Thanks to built-in query processing in the CData ODBC Driver, you know that as much query processing as possible is being pushed to Jira Assets, freeing up local resources and computing power. Download a free, 30-day trial of the ODBC Driver for Jira Assets and start working with live Jira Assets data alongside your SQL Server data today.