SQL Server Codeless Data Integration and Synchronization

Microsoft SQL Server database data can be integrated and synchronized codeless with 100+ external systems, on premises or in the cloud, using the Layer2 Cloud Connector, for example with Office 365, SharePoint, Dynamics, Exchange or Azure. You will find more supported systems and applications here.​​​​​





Benefits of Microsoft SQL Server Integration and Synchronization

​Microsoft SQL Server data integration and synchronization via Layer2 Cloud Connector has the following features and benefits.

Your SQL Server data available everywhere, at any time, on any device, or app

Connect code-free and keep your pre-selected local or cloud-based SQL Server data in sync with 100+ IT systems, such as Office 365, SharePoint, Dynamics, Exchange, Teams, and more. Make use of all features of the certain target system, such as search, forms, workflows in case of SharePoint.

High speed of implementation and low risc in project

No programming in Visual Studio or tools, such as SSIS, required. Just install the connector on a computer in your network, in the cloud, or even on your laptop and adapt predefined sample connection templates. Free Quick Start Service provided remotely, if required.

Direct secure connections under your full control

The sync runs as Windows service locally in your network our in your own cloud. No 3rd party, vendor, or cloud service is involved. Just direct connections under your full control. No changes required in the connected systems or the network.

Flexible data synchronization features for your business

Advanced features can make the difference: Flexible field mapping, Dynamic Columns to apply data cleanup, calculations, data transformation, and data translation between the connected systems to implement custom business logic in C#.

Write-back of external data changes to the SQL Server

The ADO.NET connection allows write-back of data changes made in the external system to your local or cloud-based SQL Server if required and authorized. Great to implement cross-system business processes, such as Microsoft SharePoint workflows or actions in PowerApps, Flow, or Azure Logic Apps.

No hidden costs with licensing and maintenance

Users in the connected systems are working with their system only, such as Office 365, or SharePoint. The will never access SQL Server directly. No need for any user CALs, just a one-time fee for the Layer2 Cloud Connector license. No additional costs per connected system, connection, number of transferred items, or data volume.


  • Virtually any data sources supported: ODBC, OLEDB, OData, SOAP, Microsoft .NET based providers, Files (Excel, XML, CSV, Text), RSS / XML feeds, SQL databases like MS SQLSQL Azure, Oracle, MySQL, IBM DB2, IBM AS/400, IBM Informix; Notes, SharePoint, Office 365 (lists and libraries), local file systemcloud-based file storesExchangeActive DirectoryDynamics NAV/CRM, Navision, SAP, and many more. More complex data sources, REST-based web services, custom COM, or .NET objects can be connected using 3rd-party add-ons. Cloud-to-cloud connections, e.g. to salesforce.comTwitter, Facebook, Google, Amazon, BOX.NET and others are also supported.
  • Layer2 CSOM Data Provider included: You can connect and sync your Capsule CRM data with SharePoint lists and libraries on-premise or in the Office 365 / OneDrive for Business cloud.
  • Layer2 File System Data Provider included: You can sync local files or file server shares with SharePoint Online or on-premises libraries, e.g. for backup, collaboration or mobile access. Optionally, you can sync metadata only - not the file itself. You can link to, for example, your own FTP/HTTP, to Azure, BOX, or SkyDrive / OneDrive to save space or use low-cost Office 365 plans. You can update file metadata based on SQL Server queries.
  • Layer2 OData Data Provider included: You can connect your Capsule CRM data to all OData sources, e.g. Microsoft CRM/ERP or SAP via NetWeaver.
  • Layer2 XML Data Provider included: You can connect your Capsule CRM data to any XML-based files and web requests, and filter results by using XPath query language.
  • Layer2 RSS Data Provider included: Please note that this provider is also included as sample source code to build your own provider.
  • Layer2 Exchange Data Provider included: You can sync Capsule CRM data like contacts, tasks, calendar events, notes, and email to Exchange using Exchange Web Services (EWS). Exchange 2007, 2010, and 2013 are supported as well as Exchange Online. Shared & Site Mailboxes supported.
  • Layer2 SOAP Web Services Provider included: Connect Capsule CRM to to SOAP-based web services codeless with flexible parameters.
  • Very flexible sync options: Uni- and bi-directional sync are supported. Execute a specific connection scheduled in background (Windows Service) or on demand (e.g. by command line). Sync all data or pre-selected subsets only. Select source and target folders, make use of additional no-delete, no-insert, no-update options.
  • Data type conversion included: Sync SQL data with SharePoint links, lookups, managed metadata, and more with advanced options.
  • Process integration: Raise change notifications and start workflows in the cloud, triggered on external SQL data changes. Find your SQL data changes in Delve via Office Graph. All features of native SharePoint lists and libraries are supported, e.g. views, sorting, filtering, grouping, search, mobile and offline access, social features like tagging and enterprise metadata, RSS feeds, change notifications per email, or workflows in the cloud on external data change. You can also add your own business logic.
  • Mobile and offline access: You can sync SQL Server queries with Office 365 / SharePoint Online for data access from everywhere, with any device, at any time - also offline with write-back of changes.
  • Additional unmapped "SharePoint-only" columns can be created: Ranking, rating, managed metadata, comments or file attachments.
  • Data aggregation: Multiple connections can combine several different SQL data queries into one list.
  • Flexible logging and alerts: You can log to files, databases, and Windows Event Log via NLOG.
  • Free Edition: You can test the Free Edition as long as you want or you can use in production with limited features. You can upgrade the Free Edition to a licensed version at any time without new installation.
  • Flexible, cost-effective licensing: Personal or Professional Edition, depending on requirements. Licensing per installation (no user CALs, not bound to any SharePoint server or site, just a one-time fee - no data volume-related costs). Easy to setup and maintain. You can save SQL Server user CAL license costs by providing the data in external systems - as a synchronized copy.

Microsoft SQL Server Specific Configuration Settings


In the Layer2 Cloud Connector the data source or destination entity must be configured as follows to connect to Microsoft SQL Server.


how to connect sql to office 365 2

 Fig.: SQL Server sample connection in the Layer2 Layer2 Cloud Connector



Please note the following about settings, features and possible issues.


  • Please select the SQLClient Data Provider from the list of installed providers. If you can't find, please install from Microsoft.
  • You can make use of any connection strings for SQL Server as usual, e.g.:
    Data Source=myServer; User Id=myUser; Password=myPassword.
    You will find more information about SQL Server connection strings here.
  • In case of integrated authentication (trusted connection) please make sure that the Windows Service has appropriate database access rights. Best to use basic authentication with a specific user.
  • You can make use of all SQL queries your data provider supports. You can also use stored procedures that return records, exec myStoredProcedure().
  • You can make use of aliases in the query to force auto-mapping in the Cloud Connector, e.g. select customername as title, to auto-map to a SharePoint title column.
  • The primary key is normally set automatically.
  • Bi-directional sync is supported.


Do you have any issues to connect? Please contact [email protected] for next steps.

Examples of SQL Server Integration Scenarios implemented via Layer2 Cloud Connector


You will find more information about specific scenarios here:


  • How to connect and sync SQL Server with Microsoft SharePoint or Office 365
  • Use SharePoint Online as a database front-end to your local or cloud-based SQL Server.
  • Connect and sync Microsoft SQL Server data queries with Microsoft Dynamics CRM or ERP via OData.
  • Push SQL Server data to Microsoft Exchange for mobile and offline access on any device (BYOD).
  • Make your local SQL Server data available for Microsoft PowerApps to edit on any device.
  • Keep your team members in Microsoft Teams or Office Groups notified about pre-selected SQL Server data changes.
  • Start workflows in Microsoft Flow or Azure Logic Apps on SQL Server data changes.
  • Sync external systems with SQL Server for better reporting in SSRS.

Please also note this product video at YouTube. Can't find the scenario you are looking for? Please contact [email protected] for help.

SQL Server Integration - Known Issues and Workarounds


  • Bi-directional synchronization is generally supported. Your query must be updatable for this (note that most joins are not). You also need to have write access rights to SQL for two-way sync.
  • Blobs, binary fields such as used to store images or documents in database tables are not supported by the data provider.
  • Complex SharePoint fields like lookups, user or group picker etc. are generally supported. You have to make sure providing values that fit into the fields. If not possible, you can workaround by synchronizing text fields only and add your business logic using triggers and stored procedures (in SQL) or workflows (in SharePoint).
  • You will learn more about the SQL query language here.


Please find answers to frequently asked questions about SQL Server data integration below.

Where to find valid SQL Server connection strings?

You can use any connection string your SQL Server understands, we are just passing it to the data provider. You can find examples here. For more details see SQL Server documentation.

How to fix SQL Server connectivity issues?

For basic authentication make sure that the given user/password combination is valid and the user has appropriate database access rights. If no user is given (integrated authentication or trusted mode) make sure that the Windows Service has database access. By default, this is not the case as it typically runs under a local service account. Please use a privileged domain account instead of the default account.

Where to define my insert, update, and delete SQL statements

You don't have to define any insert, update or delete SQL statements to keep the connected systems current. The data providers will generate it automatically during runtime based on your data query (select statement) and your primary key(s).


Learn more about similar solutions for data migration, backup, integration, and synchronization by vendor and topic.

Ready to go next steps?

Register for free download.

Keep your SQL Server in sync. Download and try today.

Questions? Contact us.

We are here to help. Contact us and out consulting will be happy to answer your questions.