SQL Server SharePoint Online Connector In this article you will learn how to integrate SharePoint Online data to SQL Server without coding in just a few clicks (live / bi-directional connection to SharePoint Online). SharePoint Connector can be used to integrate SharePoint and your defined data source, e.g. Microsoft SQL, Oracle, Excel, Power BI, etc. Get, write, delete SharePoint data in a few clicks!. Using SharePoint Online Connector you will be able to connect, read, and write data from within SQL Server. Follow the steps below to see how we would accomplish that. Download  Help File  Buy  Driver mentioned in this article is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc. If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started. ODBC PowerPack - System Requirements and Installation Getting Started - Using ODBC PowerPack ODBC API Driver Help File

See also Connect SharePoint Online in SSIS Connect SharePoint Online in Power BI Connect SharePoint Online in SSRS Connect SharePoint Online in Informatica Connect SharePoint Online in MS Access Connect SharePoint Online in MS Excel Connect SharePoint Online in SSAS Connect SharePoint Online in C# Connect SharePoint Online in Python Connect SharePoint Online in JAVA Connect SharePoint Online in Tableau Connect SharePoint Online in SAP Crystal Reports Connect SharePoint Online in Azure Data Factory (ADF) Connect SharePoint Online in ODBC

Video Tutorial - Integrate SharePoint Online data in SQL Server

This video covers following and more so watch carefully. After watching this video follow the steps described in this article.

• How to download / install required driver for SharePoint Online integration in SQL Server
• How to configure connection for SharePoint Online
• Features about API Driver (Authentication / Query Language / Examples / Driver UI)
• Using SharePoint Online Connection in SQL Server

Create Data Source in ZappySys Data Gateway based on ZappySys API Driver

1. Download and install ZappySys ODBC PowerPack.

2. Search for gateway in start menu and Open ZappySys Data Gateway:
   

3. Go to Users Tab to add our first Gateway user. Click Add; we will give it a name tdsuser and enter password you like to give. Check Admin option and click OK to save. We will use these details later when we create linked server:
   

4. Now we are ready to add a data source. Click Add, give data source a name (Copy this name somewhere, we will need it later) and then select Native - ZappySys API Driver. Finally, click OK.

   SharePointOnlineDSN

   
   

5. When the Configuration window appears give your data source a name if you haven't done that already, then select "SharePoint Online" from the list of Popular Connectors. If "SharePoint Online" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

   SharePointOnlineDSN

   SharePoint Online

   

6. Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

    User Credentials [OAuth]

   OAuth App must be created in Microsoft Azure AD. These settings typically found here https://docs.microsoft.com/en-us/graph/auth-register-app-v2. [Read more..]

   Steps to get SharePoint Online Credentials
   

   Firstly, login into Azure Portal and there create an OAuth application:

   1. Go to Azure Portal and login there.
   2. Then go to Azure Active Directory.
   3. On the left side click menu item App registrations
   4. Then proceed with clicking New registration.
   5. Enter a name for your application.
   6. Select Accounts in this organizational directory only as supported account type to access data in your company.
   7. In Redirect URI section leave option selected at Web.
   8. In nearby textbox enter https://login.microsoftonline.com/common/oauth2/nativeclient as Redirect URI or any other valid redirect URL, e.g. https://zappysys.com/oauth
   9. Use this Redirect URI in Redirect URL grid row.
   10. Copy Application (client) ID and paste it into API Connection Manager configuration grid in Client ID row.
   11. Then click on Endpoints link and copy first URL to Authorization URL and second one to Token URL in configuration grid. Usually they look similar to these:
       • https://login.microsoftonline.com/daed1250-xxxx-xxxx-xxxx-ef0a982d3d1e/oauth2/v2.0/authorize
       • https://login.microsoftonline.com/daed1250-xxxx-xxxx-xxxx-ef0a982d3d1e/oauth2/v2.0/token
       • https://login.microsoftonline.com/common/oauth2/v2.0/authorize
       • https://login.microsoftonline.com/common/oauth2/v2.0/token
   12. Close "Endpoints" and create a Client Secret by clicking Certificates & secrets.
   13. Proceed by clicking New client secret and setting expiration period. Copy the client secret and paste it into configuration grid in Client Secret row.
   14. Use these scopes in Scopes field: offline_access Files.Read Files.Read.All Files.ReadWrite Files.ReadWrite.All openid profile Sites.Read.All Sites.ReadWrite.All User.Read email
   15. Click Generate Token to generate tokens.
   16. That's it!

   For more information you can read this link https://docs.microsoft.com/en-us/graph/auth-register-app-v2 Also https://docs.microsoft.com/en-us/graph/auth-register-app-v2

   Fill in all required parameters and set optional parameters if needed:

   SharePointOnlineDSN

   SharePoint Online

   User Credentials [OAuth]

   https://graph.microsoft.com/v1.0

   Required Parameters
   Authorization URL	Fill in the parameter...
   Token URL	Fill in the parameter...
   Client ID	Fill in the parameter...
   Scope	Fill in the parameter...
   SiteId (select after pressing 'Generate Token')	Fill in the parameter...
   Optional Parameters
   Client Secret	Fill in the parameter...
   ReturnUrl	Fill in the parameter...
   Login Prompt Option	Fill in the parameter...
   RetryMode	Fill in the parameter...
   RetryStatusCodeList	Fill in the parameter...
   RetryCountMax	Fill in the parameter...
   RetryMultiplyWaitTime	Fill in the parameter...

   

    Application Credentials [OAuth]

   OAuth App must be created in Microsoft Azure AD. These settings typically found here https://docs.microsoft.com/en-us/graph/auth-v2-service [Read more..]

   Steps to get SharePoint Online Credentials
   

   Firstly, login into Azure Portal and there create an OAuth application:

   Step-1: Create OAuth App

   1. Go to Azure Portal and login there.
   2. Then go to Azure Active Directory.
   3. On the left side click menu item App registrations
   4. Then proceed with clicking New registration.
   5. Enter a name for your application.
   6. Select one of Accounts in this organizational directory only as supported account type to access data in your company.
   7. In Redirect URI section leave option selected at Web.
   8. Copy Application (client) ID and paste it into API Connection Manager configuration grid in Client ID row.
   9. Then click on Endpoints link and copy second, Token, URL to Token URL field in configuration grid. Usually they look similar to these:

      https://login.microsoftonline.com/daed1250-xxxx-xxxx-xxxx-ef0a982d3d1e/oauth2/v2.0/token
      https://login.microsoftonline.com/common/oauth2/v2.0/token
      

   10. Close "Endpoints" and create a Client Secret by clicking Certificates & secrets.
   11. Proceed by clicking New client secret and setting expiration period. Copy the client secret and paste it into configuration grid in Client Secret row.
   12. Go to API Permissions section and add Microsoft Graph permissions for SharePoint and Drive, e.g. Sites.Selected, Sites.Read.All, Sites.ReadWrite.All, Files.Read.All, Files.ReadWrite.All.
   13. Finally, Grant admin consent for your domain for your permissions.

   Step-2: Register OAuth App in SharePoint Admin Portal

   1. After we create OAuth App we need to add grant SharePoint access to that App using Admin Portal. Make sure you have admin permission to acces Portal. For detailed steps you may refer to this link. Here are basic steps you can follow.
   2. Log in to SharePoint Admin Portal and access below URL
      (Replace YOURCOMPANY)
      

      https://YOURCOMPANY-admin.sharepoint.com/_layouts/15/appprincipals.aspx?Scope=Web

   3. Enter App Id and other information
   4. Enter XML snippet which describes which permission you want to grant. Here is an example permission (App with FullControl / Read / Write)

      <AppPermissionRequests AllowAppOnlyPolicy="true">
        <AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="FullControl" />
      </AppPermissionRequests>
        

   5. Click Add to grant the permission. That's it!

   NOTE: After adding App in SharePoint if you ever remove the permission then you can visit the following URL and delete the App.
   

   https://YOURCOMPANY-admin.sharepoint.com/_layouts/15/appprincipals.aspx?Scope=Web

   Fill in all required parameters and set optional parameters if needed:

   SharePointOnlineDSN

   SharePoint Online

   Application Credentials [OAuth]

   https://graph.microsoft.com/v1.0

   Required Parameters
   Token URL	Fill in the parameter...
   Client ID	Fill in the parameter...
   Client Secret	Fill in the parameter...
   SiteId	Fill in the parameter...
   Optional Parameters
   Scope	Fill in the parameter...
   RetryMode	Fill in the parameter...
   RetryStatusCodeList	Fill in the parameter...
   RetryCountMax	Fill in the parameter...
   RetryMultiplyWaitTime	Fill in the parameter...

   

7. Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
   

8. Click OK to finish creating the data source.

Read data in SQL Server from the ZappySys Data Gateway data source

1. To read the data in SQL Server the first thing you have to do is create a Linked Server. Go to SQL Server Management Studio and configure it in a similar way:

2. Then click on Security option and configure username we created in ZappySys Data Gateway in one of the previous steps:

3. Finally, open a new query and execute a query we saved in one of the previous steps:
   

   SELECT * FROM OPENQUERY([MY_LINKED_SERVER_NAME], 'SELECT * FROM Products');

   

Firewall settings

So far we have assumed that Gateway is running on the same machine as SQL Server. However there will be a case when ZappySys ODBC PowerPack is installed on a different machine than SQL Server. In such case you may have to perform additional Firewall configurations. On most computers firewall settings wont allow outside traffic to ZappySys Data Gateway. In such case perform following steps to allow other machines to connect to Gateway.

Method-1 (Preferred)

If you are using newer version of ZappySys Data Gateway then adding firewall rule is just a single click.

1. Search for gateway in start menu and open ZappySys Data Gateway.
2. Go to Firewall Tab and click Add Firewall Rule button like below. This will create Firewall rule to all Inbound Traffic on Port 5000 (Unless you changed it).

Method-2 Here is another way to add / edit Inbound Traffic rule in windows firewall. Use below method if you choose to customize your rule (for advanced users).

1. Search for Windows Firewall Advanced Security in start menu.
2. Under Inbound Rules > Right click and click [New Rule] >> Click Next
3. Select Port on Rule Type >> Click Next
4. Click on TCP and enter port number under specified local port as 5000 (use different one if you changed Default port) >> Click Next
5. Select Profile (i.e. Private, Public) >> Click Next
6. Enter Rule name [i.e. ZappySys Data Gateway – Allow Inbound ] >> Click Next
7. Click OK to save the rule

OPENQUERY vs EXEC (handling larger SQL text)

So far we have seen examples of using OPENQUERY. It allows us to send pass-through query at remote server. The biggest limitation of OPENQUERY is it doesn't allow you to use variables inside SQL so often we have to use unpleasant looking dynamic SQL (Lots of tick, tick …. and escape hell). Well there is good news. With SQL 2005 and later you can use EXEC(your_sql) AT your_linked_server syntax . Disadvantage of EXEC AT is you cannot do SELECT INTO like OPENQUERY. Also you cannot perform JOIN like below in EXEC AT

    SELECT a.* FROM OPENQUERY(ls_json,'select * from value') a
    JOIN OPENQUERY(ls_json,'select * from value') b ON a.id=b.id;

However you can always do INSERT INTO MyTable EXEC(…) AT LINKEDSRV. So table must exists when you do that way. Here is how to use it. To use EXEC AT you must turn on RPC OUT option. Notice how we used variable in SQL to make it dynamic. This is much cleaner than previous approach we saw.

USE [master]
GO

EXEC master.dbo.sp_addlinkedserver @server = N'ls_Json', @srvproduct=N'', @provider=N'SQLNCLI', @datasrc=N'localhost,5000', @provstr=N'Network Library=DBMSSOCN;', @catalog=N'JsonApi';
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'ls_Json',@useself=N'False',@locallogin=NULL,@rmtuser=N'tdsuser',@rmtpassword='########';
GO

EXEC sp_serveroption 'ls_Json', 'rpc out', true;
go

declare @tbl varchar(100)='$';
EXEC('select * from ' + @tbl ) AT ls_Json;

Here is the difference between OPENQUERY vs EXEC approaches:

Create Custom Store Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
   

2. Enter the desired Procedure name and click on OK:
   

3. Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store procedure in the ZappySys Driver:
   Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
   

   CREATE PROCEDURE [usp_get_orders]
       @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
    AS
       SELECT * FROM Orders where OrderDate >= '<@fromdate>';
   

   
   

4. That's it now go to Preview Tab and Execute your Store Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
   

   Exec usp_get_orders '1996-01-01';

   
   

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

1. Go to Custom Objects Tab and Click on Add button and Select Add Table:
   

2. Enter the desired Table name and click on OK:
   

3. And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.

4. Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
   Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
   

   SELECT
     "ShipCountry",
     "OrderID",
     "CustomerID",
     "EmployeeID",
     "OrderDate",
     "RequiredDate",
     "ShippedDate",
     "ShipVia",
     "Freight",
     "ShipName",
     "ShipAddress",
     "ShipCity",
     "ShipRegion",
     "ShipPostalCode"
   FROM "Orders"
   Where "ShipCountry"='USA'

   
   

5. That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
   

   SELECT * FROM "vt__usa_orders_only"

   
   

Conclusion

In this article we discussed how to connect to SharePoint Online in SQL Server and integrate data without any coding. Click here to Download SharePoint Online Connector for SQL Server and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download SharePoint Online Connector for SQL Server Documentation 

Actions supported by SharePoint Online Connector

SharePoint Online Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.

Other App Integration scenarios for SharePoint Online

Other Connectors for SQL Server

Download SharePoint Online Connector for SQL Server Documentation 

Common Searches: