In order to perform a successful connection to your MS SQL database we just need the following information and that's it!

  1. Username and Password: Valid username and password to connect to the database.
  2. Server Address: This is the IP address of the server where the database is located or an address with the form example.database.windows.net
  3. Database: This is the name of the database we are going to connect in order to fetch the data.
  4. Table: The name of the table or tables we are going to use in order to fetch the data.
  5. Encryption: If you want the connection to be encrypted please let us know, the connection to Azure Databases will always be encrypted.

Once we have a successful connection, it will enable us to populate your AlertFind instance with  information such as:

  • ID
  • First Name
  • Middle Name
  • Last Name
  • Email
  • Personal Email
  • Cell Phone
  • Home Phone
  • Alternate Phone
  • Phone Extension
  • Company
  • Job Title
  • Department
  • Country
  • State
  • City
  • Address
  • Zip Code

How does our MS SQL Connector Works

The below graphic explains the various nodes involved in the transition of data from your MS SQL database to AlertFind.

Detailed Steps Explaining Above Graphic:

  1. MS SQL connector fetches the user information stored in your MS SQL database via API.
  2. Based on your chosen frequency, our connector running on AWS Lambda, fetches data from MS SQL database.
  3. At this stage, data goes through the validation and processing and is finally transformed into a CSV.
  4. The CSV is compressed to a Zip File and sent to AlertFind API via the AlertFind connector running on AWS Lambda.

Data Storage Nodes in the Graphic Above:

  1. Node 5: Refers to Apache Cassandra Cluster which stores the data foe execution purposes. It has a TTL of 7 days after workflow execution has finished.
  2. Node 6: Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
  3. Data Safety: All Data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames, passwords are encrypted at rest using Amazon Key Management Service (KMS) which uses FIPS 140-2 validated hardware security modules.

We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.

Did this answer your question?