Basic Errors in Stretch Database – Part 2

ByHariharan Rajendran

Basic Errors in Stretch Database – Part 2

Beginners Errors in Stretch Database SQL Server 2016 – Part 2

Check out the first basic error that beginners would experience while configuring stretch database in my previous article,

Basic Errors in Stretch Database

Another common error that usually occurred during the configuration is “Firewall”. If firewall is not able to identify the client IP address then it will throw an error like below.

Check the log to identify the detailed error message.

Error Message:

Client with IP address XXX.XXX.XX.XX is not allowed to access the server.

To fix the above issue, we have two ways.

Way 1:

Add the client IP in Azure SQL Server firewall.

Follow the below steps to add the client ip.

This will be applicable when you have SQL Server (Logical server) in Azure.
Step 1: Go to the SQL Server in Azure Portal

Step 2: Choose “Firewall”

Step 3: Click + Add Client IP and Save

Way 2:

Use the below stored procedure to add the IP Address in master database to allow the firewall.

sp_set_firewall_rule [@name = ] ‘name’,

[@start_ip_address =] ‘start_ip_address’,

[@end_ip_address =] ‘end_ip_address’

[ ; ]

Refer: https://msdn.microsoft.com/en-us/library/dn270017.aspx

About the Author

Hariharan Rajendran author

Hariharan Rajendran is a Microsoft Certified Trainer and Lead BI Solutions Consultant with 8+ years of experience in Database, BI and Azure platforms. Hariharan is also an active community leader, speaker & organizer and leads the Microsoft PUG (Power BI User Group – Chennai), SQLPASS Power BI Local Group – Chennai and an active speaker in SQL Server Chennai User Group and also a leader in Data Awareness Program worldwide events. Hariharan also frequently blogs (www.dataap.org/blog), provides virtual training (on ad-hoc basis) on Microsoft Azure, Database Administration, Power BI and database development to worldwide clients/audience.

Leave a Reply