DataSunrise Achieves AWS Data & Analytics Competency. Learn more →

This website stores cookies to collect information about how you interact with our website. To find out more visit our Privacy Policy.

  • Home
  • Guides
  • Integrate DataSunrise with SQL Server Always On Cluster

Integrate DataSunrise with SQL Server Always On Cluster

How to Migrate DataSunrise CloudFormation Template from Launch Configuration (LC) to Launch Template (LT) Resource in Auto Scaling Group How to Send DataSunrise Events to a Microsoft Teams Channel via Incoming Webhook using Subscribers How To Offload The Audit Database Data To AWS S3 And Read It Using AWS Athena Service Convert Trial or BYOL Configuration of DataSunrise to Hourly Billing PostgreSQL (RDS) vs Aurora PostgreSQL How to Troubleshoot “Connection Was Terminated” or “Connection Terminated Unexpectedly” Errors in Applications Using DataSunrise Proxies DataSunrise’s Performance Under High Traffic Conditions DataSunrise’s Approach to Configuring Penalties for SQL Injection Detection How to Block Specific Hosts in DataSunrise for Enhanced Database Security Troubleshooting AWS Metering and Hourly Billing Issues in DataSunrise on AWS Marketplace How To Perform Cloud Formation Modification Dynamic Data Masking with DataSunrise: Masking with Lua scripts How to Choose the Database for Audit Storage: A Performance Analysis How to Run pgbench Through DataSunrise Proxy on PostgreSQL 14 with SCRAM Authentication DataSunrise SSO Authentication Based on SAML (Okta) DataSunrise SSO Authentication Based on OpenID (Okta) Comprehensive Guide On How to Search for Sensitive Data in Images Hosted on AWS S3 How to Deploy DataSunrise with Terraform Template on Azure Integrate DataSunrise with SQL Server Always On Cluster How to Deploy DataSunrise in Microsoft Azure Using Azure Resource Manager How to Perform DataSunrise Static Data Masking for MongoDB How to Configure DB Audit Trailing for MS Azure MySQL Configure DB Audit Trailing for MS Azure PostgreSQL How to Configure DataSunrise to Mask Data for Amazon Athena How to Upgrade RHEL OS version of existing DataSunrise servers How to Integrate DataSunrise with AWS Database Activity Streams for Getting Auditing Results for AWS Aurora PostgreSQL Set Up SSL Certificates for DataSunrise Database Proxy Reports in DataSunrise: Crucial System for Enhanced Database Security How to Hide Schemas From Users in Redshift AWS RDS PostgreSQL Audit Logs in DataSunrise Audit Administrative Actions in Your Oracle RDS and EC2 How to Check if DataSunrise Receives Traffic Remove a Procedure or a Function From a Database

DataSunrise application can protect not only single node database servers but also cluster type database servers. Let us take a deep look into integration of DataSunrise application with SQL Server Always On Cluster.

An availability group supports a replicated environment for a discrete set of user databases, known as availability databases (please, check Microsoft SQL Server official documentation for further reference). There are two types of availability groups in SQL Server cluster architecture:

  • Always On availability group to provide high availability, disaster recovery, and read-scale balancing.
  • Read-scale availability group.

Integration Between Always On Cluster and DataSunrise

Let’s consider the traffic processing diagram within and between:

  1. Always On availability group (Part 1):
  2. DataSunrise (Part 2):

Image 1: Traffic between Always On Cluster and DataSunrise

Connection to Always On Cluster without DataSunrise:

  1. Client connects to Availability Group listener.
  2. Availability Group listener in return redirects the connection to worker 3 by the port range 11000 – 11999. The port configuration is managed by the Load Balancer itself.
  3. Now the connection is established between client application and worker 3 that connects to the database.

Basically, the initial Always-On availability cluster infrastructure is replicated when DataSunrise proxy is integrated.

Connection to Always On Cluster with DataSunrise:

  1. Client connects to listener’s proxy.
  2. The proxy redirects traffic to the original availability group listener of Always On Cluster.
  3. The AG listener then transfers the connection to worker 3 of Always On Cluster.
  4. DataSunrise protects the connection and creates a proxy 3 to protect worker 3. The traffic is directed to proxy 3.
  5. The connection is established with proxy 3.

The proxies 1-2 do not exist yet. They will be created once the listener decides to use workers 1-2.

The target database proxy configuration page will be displayed as below:

Image 2: Database Proxy Configuration

Connection to Always On Cluster Through the DataSunrise Proxy

In order to establish the connection to SQL Server Always On Cluster, it will be necessary to connect to the server by specifying DataSunrise IP address and proxy port from the instance configuration:

Image 3: Connection to Datasunrise Proxy

Now DataSunrise application can protect not only single node database servers but also cluster type database servers.

Did this guide help you?

Contact Us