Microsoft SQL Server (aka SQL Server) comes in many versions and is deployed in many ways - on-prem, in the cloud, hybrid cloud, etc. Direct connection and CSV export via SFTP are currently supported.
Option 1: Direct connection
If your SQL Server is accessible from the public internet, even if it is behind a firewall, then we can connect securely to it directly via our pre-built integration. For example, if you are running on Amazon RDS for SQL Server or on a corporate network with a public endpoint. You can whitelist Faraday's IPs to increase security. All we'll need are connection details for a read-only user.
Go to the Faraday app’s Sources console, click Create source at the top.
Search for Microsoft SQL Server as a Source location, enter a descriptive name, and click Next.
Enter your Microsoft SQL Server details, and click Next.
Under Finalize, click Create source. Faraday can now begin the integration process. Once you finalize this source integration, our Customer Success team will be able to finish the configuration and we can begin utilizing your Microsoft SQL Server data!
Option 2: CSV export via SFTP (SSH File Transfer Protocol)
If your SQL Server is not accessible from the public internet, which is very common for on-prem installations, you can schedule a CSV export and transfer via SFTP. Even within SFTP, there are options - you can give us access to your corporate SFTP server, or upload directly to our SFTP server. Faraday uses AWS Transfer for SFTP which is the industry gold standard for security.
Ensure CSV formatting is correct
If you are using CSV export, you have to configure SQL Server to properly export CSVs. By default, SQL Server produces a completely bizarre and non-standard CSV output. This is well-documented in the industry.
These are the most important settings:
In case you are also saving query results as CSV, be sure to set these:
Send CSV via SFTP
Now you can use your job scheduler and file transfer client of choice to send the CSV to Faraday.