question

Clodola avatar image
0 Votes"
Clodola asked OuryBa-MSFT edited

SSDT 2017/2019 -- will not connect to Azure managed sql Instance


All updates are installed on VS 2017 (15.9.47) and 2019 (16.11.13)
Windows updates installed
PC restarted

I am trying to perform a data comparison between two DB's , On Prem and Azure SQL managed instance
Everything has been working fine for the last few months

I changed my password last week , this is the only thing I can see causing issue?
When I changed my password previously , I had no issues , maybe coincidence

I can connect to the Azure SQL managed instance in SSMS with new password
I can connect to the Azure SQL managed instance in SSDT with new password

Issue

In SSDT --> Tools --> SQL Server --> New data comparison --> Select connection

Select the Azure SQL managed instance , click connect --> connecting --> prompts for my password
No error --> in the Source Database still illustrates "choose a database" (should illustrate the Azure SQL managed instance)

Using On-prem Server connects fine

  • created a new connection to the Azure SQL managed instance in SSDT with new password , I can see all databases , no errors

    • Same issue in SSDT Schema comparison tool

    • Azure Data Studio Schema comparison tool works comparing on-Prem to Azure managed instance (No data comparison tool)


Azure Data studio , you can get an error after you change your AAD password , Token dies and does not refresh
You will find that after about 2 weeks the token dies and will not refresh as you would expect. No amount of trying to open a new connection will trigger the re-auth process.
Solution: Close Azure Data Studio and delete the cached token here:
C:\Users\YOUR_USERNAME\AppData\Roaming\azuredatastudio\Azure Accounts


Something similar happening here?




azure-sql-database
· 2
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

OuryBa-MSFT avatar image OuryBa-MSFT ·

Thank you @Clodola for reporting your issue on Microsoft Q&A.

We are not seeing customers reported this issue, but we will definitely try to test that from our end and see if we will see the same behavior.

Regards,
Oury

0 Votes 0 ·
Clodola avatar image Clodola OuryBa-MSFT ·

Alot of customers have this issue , due to Microsoft update on sql managed instance

https://docs.microsoft.com/en-us/answers/questions/783680/is-sql-managed-instance-no-longer-compatible-with.html

0 Votes 0 ·

1 Answer

OuryBa-MSFT avatar image
0 Votes"
OuryBa-MSFT answered OuryBa-MSFT edited

@Clodola Got it. Thank you for clarifying this. https://docs.microsoft.com/en-us/answers/questions/782571/index.html
There was an update from the Product Group on this issue.

The fix for this issue is available in Visual Studio 2022 Preview (Version 17.2.0 Preview 3.0).
As short-term mitigation we suggest customers install Visual Studio 2022 Preview. This version can be installed side-by-side with other versions, and can be downloaded from https://visualstudio.microsoft.com/vs/preview/#download-preview
As a long-term mitigation, once the fix reaches the Visual Studio 2022 GA editions (version 17.2.0 or higher), we suggest customers start using Visual Studio 2022 GA (Community, Professional, Enterprise). There is currently no ETA for this fix to reach Visual Studio 2019.
Note that the use of Visual Studio 2022 Community is permitted for organizations of any size when used for SQL Server Data Tools development (the software license terms is available at https://visualstudio.microsoft.com/license-terms/vs2022-ga-community/).
Visual Studio (GA) can be downloaded from https://visualstudio.microsoft.com/downloads/

We apologize for the impact. We are continuously taking steps to improve the Microsoft Azure Platform and our processes to help ensure such incidents do not occur in the future

Regards,
Oury

5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.