Unable to use Azure SQL managed instance (public instance) for Quick Sight dataset

Q&A
, ,
1

I have the database hosted with Azure SQL managed instance

I can connect to the public instance of it but when I try to use the same connection information to connect Quick Sight dataset with the database, I get error when connecting.

I did a lot of research and configure in Azure but the result is the same.

Can someone help me confirm that the Azure SQL managed instance can or cannot work with AWS Quick Sight?

Thanks in advance.

2

Hi @truongth91

Welcome to the Quick Sight community!

Please verify that your database version is supported by Quick Sight by checking the official list of data sources supported by Quick Sight. Specifically, ensure that you are using Microsoft SQL Server 2012 or later if you plan to connect Quick Sight to a Microsoft SQL database. This is important because Quick Sight requires this minimum version for SQL Server connections to work correctly.

Additionally, please share the exact error message you receive when trying to connect and provide database details such as the version and whether your database is running on an Azure VM.

3

Hello @Xclipse ,

Thanks for the swift response.

I am using an Azure SQL managed instance, and per this document (What is the Azure SQL Database service? - Azure SQL Database | Microsoft Learn), it should run the latest MS SQL Server.

To add more context about the issue:

  1. This is the SQL service provided by Azure. I believe it is similar to AWS RDS
  2. There are 2 ways to connect to this database, using a private or public address. I am sure that I am using the public address to connect. Tested it with SSMS, but every time I tried with Quick Sight (Add new dataset, it always gives me the below error)
Cannot open server "database.windows.net" requested by the login. The login failed.

I tried:

  1. Update the SNG in Azure Resources to allow the Quick Sight IP addresses
  2. Check the Route Table

And nothing works.

If you have any experience with this, please give me some advice.

Thanks.

4

Hi @truongth91

Could you please try connecting to SQL Server using the format below. The connector often requires the username to be formatted as username@servername rather than just username. Please also try connecting with SSL disabled.

Also, ensure that the relevant Quick Sight IP ranges are allowed in your Azure firewall settings so that network traffic from Quick Sight is not blocked.

5

Hi @Xclipse ,

I am sorry for taking so long to respond, but anyway, I tried your suggestion, and it does not work:

  1. I only have the public option

  2. If I input the username with the @ format, it throws this error (and I am sure that I can access the database with SSMS with the user and password without the @ part):

    image
    image731×273 17.8 KB

  3. I did configure the Network Security group in Azure to allow the Quick Sight IP ranges, but still, it is still not working.

6

Here the image of public option only

image
image709×309 13.6 KB

7

Hi @truongth91

Sorry, I’m out of ideas. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!