Connect to SQL Server Data in ACL Analytics

ACL Analytics, part of Diligent HighBond, is a powerful data analysis software primarily used for audit, risk management, and compliance. It enables professionals to examine and analyze large volumes of data to identify anomalies, trends, and potential risks or fraudulent activities.

CData Connect AI offers a dedicated cloud-to-cloud interface for SQL Server, enabling analytics directly from live SQL Server data within ACL Analytics, all without the need for data replication to a native database. With its inherent optimized data processing capabilities, CData Connect AI efficiently channels all supported SQL operations, including filters and JOINs, directly to SQL Server. This leverages server-side processing to swiftly deliver the requested SQL Server data.

Configure SQL Server Connectivity for ACL Analytics

Connectivity to SQL Server from ACL Analytics is made possible through CData Connect AI. To work with SQL Server data from ACL Analytics, we start by creating and configuring a SQL Server connection in CData Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a Connection

2. Select "SQL Server" from the Add Connection panel
👁 Selecting a data source

3. Enter the necessary authentication properties to connect to SQL Server. Enter the necessary authentication properties to connect to SQL Server.

   Connecting to Microsoft SQL Server

   Connect to Microsoft SQL Server using the following properties:

   • Server: The name of the server running SQL Server.
   • User: The username provided for authentication with SQL Server.
   • Password: The password associated with the authenticating user.
   • Database: The name of the SQL Server database.

   Connecting to Azure SQL Server and Azure Data Warehouse

   You can authenticate to Azure SQL Server or Azure Data Warehouse by setting the following connection properties:

   • Server: The server running Azure. You can find this by logging into the Azure portal and navigating to "SQL databases" (or "SQL data warehouses") -> "Select your database" -> "Overview" -> "Server name."
   • User: The name of the user authenticating to Azure.
   • Password: The password associated with the authenticating user.
   • Database: The name of the database, as seen in the Azure portal on the SQL databases (or SQL warehouses) page.

   SSH Connectivity for SQL Server

   You can use SSH (Secure Shell) to authenticate with SQL Server, whether the instance is hosted on-premises or in supported cloud environments. SSH authentication ensures that access is encrypted (as compared to direct network connections).

   SSH Connections to SQL Server in Password Auth Mode

   To connect to SQL Server via SSH in Password Auth mode, set the following connection properties:

   • User: SQL Server User name
   • Password: SQL Server Password
   • Database: SQL Server database name
   • Server: SQL Server Server name
   • Port: SQL Server port number like 3306
   • UserSSH: "true"
   • SSHAuthMode: "Password"
   • SSHPort: SSH Port number
   • SSHServer: SSH Server name
   • SSHUser: SSH User name
   • SSHPassword: SSH Password

   SSH Connections to SQL Server in Public Key Auth Mode

   To connect to SQL Server via SSH in Password Auth mode, set the following connection properties:

   • User: SQL Server User name
   • Password: SQL Server Password
   • Database: SQL Server database name
   • Server: SQL Server Server name
   • Port: SQL Server port number like 3306
   • UserSSH: "true"
   • SSHAuthMode: "Public_Key"
   • SSHPort: SSH Port number
   • SSHServer: SSH Server name
   • SSHUser: SSH User name
   • SSHClientCret: the path for the public key certificate file
   👁 Configuring a connection (Salesforce is shown)
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add SQL Server Connection page and update the User-based permissions. 👁 Updating permissions
   

Add a Personal Access Token

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.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create. 👁 Creating a new PAT
   
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to SQL Server data from ACL Analytics.

Connect to SQL Server from ACL Analytics

The steps below outline connecting to CData Connect AI from ACL Analytics to create a new SQL Server data source. The CData Connect AI Virtual SQL Server allows you to establish a connection to your data from integration tools that support connections to SQL servers. The Virtual SQL Server mimics the behavior of a traditional SQL server, and it supports a range of query options.

1. With your Analytics File open, select 'Import' --> 'Database and application' 👁 Creating a new data source
   
2. Create a new connection
3. Set the connection information
   • Server: tds.cdata.com
   • Port: 14333
   • Auth Scheme: Password
   • Username: a Connect AI user, for example, [email protected]
   • Password: the PAT for the above Connect AI user
   • Database: the name of your SQL Server connection, for example, SQL1
   👁 Connecting to Connect AI
   
4. Click "Test Connection"
5. Click "OK"
6. You are now ready to work with your SQL Server data in ACL Analytics! 👁 See your data in ACL Analytics
   

Live connections to SQL Server data from your applications

ACL Analytics can now connect to live SQL Server data directly through Connect AI, allowing you to analyze SQL Server data without duplicating it.

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your applications, try CData Connect AI today!