How to connect PolyBase to Facebook

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 Facebook, you get access to your Facebook data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live Facebook 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 Facebook data using PolyBase due to optimized data processing built into the driver. When you issue complex SQL queries from SQL Server to Facebook, the driver pushes down supported SQL operations, like filters and aggregations, directly to Facebook 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 Facebook data, using a single query to pull data from distributed sources.

Connect to Facebook

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

Most tables require user authentication as well as application authentication. Facebook uses the OAuth authentication standard. To authenticate to Facebook, you can use the embedded OAuthClientId, OAuthClientSecret, and CallbackURL or you can obtain your own by registering an app with Facebook.

See the Getting Started chapter of the help documentation for a guide to using OAuth.

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

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

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

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

Create an External Data Source for Facebook

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

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

For Facebook, 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_facebook_source
WITH ( 
  LOCATION = 'odbc://SERVER_URL',
  CONNECTION_OPTIONS = 'DSN=CData Facebook Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = facebook_creds
);

Create External Tables for Facebook

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

CREATE EXTERNAL TABLE Posts(
  FromName [nvarchar](255) NULL,
  LikesCount [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Posts',
  DATA_SOURCE=cdata_facebook_source
);

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