![]() |
VOOZH | about |
SQL Server Linked Servers enable the SQL Server Database Engine to read data from remote data sources and execute commands against the remote database servers outside of the instance of SQL Server. Typically, linked servers are configured to enable the execution of a T-SQL statement that includes tables in another instance of SQL Server, or another database product such as Oracle. When paired with CData Connect AI, linked servers provides instant access to Paylocity data from your SQL Server database. This article demonstrates how to connect to Paylocity using Connect AI and query Paylocity data in SQL Server Management Studio (SSMS).
CData Connect AI provides a pure SQL Server interface for Paylocity, allowing you to query data from Paylocity without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to Paylocity, leveraging server-side processing to return the requested Paylocity data quickly.
Connectivity to Paylocity from SQL Linked Servers is made possible through CData Connect AI. To work with Paylocity data from SQL Linked Servers, we start by creating and configuring a Paylocity connection.
Set the following to establish a connection to Paylocity:
This property is required for executing Insert and Update statements, and it is not required if the feature is disabled.
Paylocity will decrypt the AES key using RSA decryption.
It is an optional property if the IV value not provided, The driver will generate a key internally.
You must use OAuth to authenticate with Paylocity. OAuth requires the authenticating user to interact with Paylocity using the browser. For more information, refer to the OAuth section in the Help documentation.
The Pay Entry API is completely separate from the rest of the Paylocity API. It uses a separate Client ID and Secret, and must be explicitly requested from Paylocity for access to be granted for an account. The Pay Entry API allows you to automatically submit payroll information for individual employees, and little else. Due to the extremely limited nature of what is offered by the Pay Entry API, we have elected not to give it a separate schema, but it may be enabled via the UsePayEntryAPI connection property.
Please be aware that when setting UsePayEntryAPI to true, you may only use the CreatePayEntryImportBatch & MergePayEntryImportBatchgtable stored procedures, the
InputTimeEntry table, and the OAuth stored procedures. Attempts to use other features of the product will result in an error. You must also store your OAuthAccessToken
separately, which often means setting a different OAuthSettingsLocation when using this connection property.
π Configuring a connection (Salesforce is shown)
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the connection configured and a PAT generated, you are ready to connect to Paylocity data from .
To establish a connection from SQL Server Linked Server to the CData Connect AI Virtual SQL Server API, follow these steps.
You can now execute queries to the Paylocity linked server from any tool that can connect to SQL Server. An example SQL query would be:
SELECT * FROM [CDATA CONNECT CLOUD].[Paylocity1].[Paylocity].[Employee]π Querying live data in SQL Server Management Studio (Excel Online is shown)
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your SQL Server database, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial