Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →How to connect PolyBase to Microsoft Teams
Use CData drivers and PolyBase to create an external data source in SQL Server 2019 with access to live Microsoft Teams 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 Microsoft Teams, you get access to your Microsoft Teams data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live Microsoft Teams 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 Microsoft Teams data using PolyBase due to optimized data processing built into the driver. When you issue complex SQL queries from SQL Server to Microsoft Teams, the driver pushes down supported SQL operations, like filters and aggregations, directly to Microsoft Teams 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 Microsoft Teams data, using a single query to pull data from distributed sources.
Connect to Microsoft Teams
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 Microsoft Teams Sys is created automatically).
You can connect to MS Teams using the embedded OAuth connectivity. When you connect, the MS Teams OAuth endpoint opens in your browser. Log in and grant permissions to complete the OAuth process. See the OAuth section in the online Help documentation for more information on other OAuth authentication flows.
Click "Test Connection" to ensure that the DSN is connected to Microsoft Teams properly. Navigate to the Tables tab to review the table definitions for Microsoft Teams.
Create an External Data Source for Microsoft Teams 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 Microsoft Teams data.
NOTE: Since Microsoft Teams does not require a User or Password to authenticate, you may use whatever values you wish for IDENTITY and SECRET.
CREATE DATABASE SCOPED CREDENTIAL msteams_creds WITH IDENTITY = 'username', SECRET = 'password';
Create an External Data Source for Microsoft Teams
Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for Microsoft Teams with PolyBase:
- Set the LOCATION parameter , using the DSN and credentials configured earlier.
For Microsoft Teams, 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_msteams_source WITH ( LOCATION = 'odbc://SERVER_URL', CONNECTION_OPTIONS = 'DSN=CData Microsoft Teams Sys', -- PUSHDOWN = ON | OFF, CREDENTIAL = msteams_creds );
Create External Tables for Microsoft Teams
After creating the external data source, use CREATE EXTERNAL TABLE statements to link to Microsoft Teams data from your SQL Server instance. The table column definitions must match those exposed by the CData ODBC Driver for Microsoft Teams. 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 Microsoft Teams Teams would look similar to the following:
CREATE EXTERNAL TABLE Teams( subject [nvarchar](255) NULL, location_displayName [nvarchar](255) NULL, ... ) WITH ( LOCATION='Teams', DATA_SOURCE=cdata_msteams_source );
Having created external tables for Microsoft Teams 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 Microsoft Teams, freeing up local resources and computing power. Download a free, 30-day trial of the ODBC Driver for Microsoft Teams and start working with live Microsoft Teams data alongside your SQL Server data today.