Connect to Twitter Ads as an External Data Source using PolyBase

Ready to get started?

Download for a free trial:

Download Now

Learn more:

Twitter Ads ODBC Driver

The Twitter Ads ODBC Driver is a powerful tool that allows you to connect with live data from Twitter Ads, directly from any applications that support ODBC connectivity.

Access Twitter Ads data like you would a database - read, write, and update Twitter Ads Accounts, Campaigns, Stats, Tweets, etc. through a standard ODBC Driver interface.



Use the CData ODBC Driver for Twitter Ads and PolyBase to create an external data source in SQL Server 2019 with access to live Twitter Ads data.

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 Twitter Ads, you get access to your Twitter Ads data directly alongside your SQL Server data. This article walks through creating an external data source and external tables to grant access to live Twitter Ads data using T-SQL queries.

The CData ODBC drivers offer unmatched performance for interacting with live Twitter Ads data using PolyBase due to optimized data processing built into the driver. When you issue complex SQL queries from SQL Server to Twitter Ads, the driver pushes down supported SQL operations, like filters and aggregations, directly to Twitter Ads 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 Twitter Ads data, using a single query to pull data from distributed sources.

Connect to Twitter Ads

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 Twitter Ads Sys is created automatically).

All tables require authentication. You must use OAuth to authenticate with Twitter. OAuth requires the authenticating user to interact with Twitter using the browser. For more information, refer to the OAuth section in the Help documentation.

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

Create an External Data Source for Twitter Ads 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 Twitter Ads data.

NOTE: Since Twitter Ads does not require a User or Password to authenticate, you may use whatever values you wish for IDENTITY and SECRET.

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

Create an External Data Source for Twitter Ads

Execute the following SQL command to create an external data source for Twitter Ads with PolyBase, using the DSN and credentials configured earlier.

For Twitter Ads, set SERVERNAME to 'localhost' or '127.0.0.1' and 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_twitterads_source
WITH ( 
  LOCATION = 'odbc://SERVERNAME[:PORT]',
  CONNECTION_OPTIONS = 'DSN=CData Twitter Ads Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = twitterads_creds
);

Create External Tables for Twitter Ads

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to Twitter Ads data from your SQL Server instance. The table column definitions must match those exposed by the CData ODBC Driver for Twitter Ads. 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 Twitter Ads AdStats would look similar to the following:

CREATE EXTERNAL TABLE AdStats(
  EntityId [nvarchar](255) NULL,
  Entity [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='AdStats',
  DATA_SOURCE=cdata_twitterads_source
);

Having created external tables for Twitter Ads 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 Twitter Ads, freeing up local resources and computing power. Download a free, 30-day trial of the ODBC Driver for Twitter Ads and start working with live Twitter Ads data alongside your SQL Server data today.