This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
VS Version: 2022 and 2019 (with latest SSDT updates).
Since one of our Azure SQL Manages Instances was updated yesterday we cannot access it in Visual Studio anymore.
Error message: "An incompatible SQL Server version was detected."
The managed instances which haven't gotten the update yet still work.
@Thomas Totter Thank you for posting your question on Microsoft Q&A and for using Azure services.
My understanding is that you are unable to access your Managed Instance from visual studio after of the Managed Instance was updated to a different version.
You are able to access to the one which were not updated. Please let me know if my understanding is not correct. I will suggest you create a support ticket for this type of issue.
Please let me know if you don't have a support plan. I will make sure to unable one for you.
Regards,
Oury
Your understanding of the situation is 100% correct!
Thanks for the advice regarding ticket. My company (or in that case our customer) will open a support ticket (i requested this internally yesterday already). But since this might take 2-3 days on their side, i just wanted to check if anyone here experiences the same issues and (maybe) found some workaround etc.
If i get some infos on the matter, i'll update here if it's not a specific problem on our side.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 1%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
We are experiencing the same issues. Both Visual Studio 2019 and 2022.
No issues when connection to SQL Elastic Pool
@Thomas Totter , @AreHH , anonymous user, @JUMARIE Fabrice , @Butler Jonathan
The Product team is working on this, and we will provide updates regarding this situation on this thread. Soonest is Mid-April.
Thank you for your patience
Regards,
Oury
Soonest is Mid-April.
Ouch. Can the Product team(s) suggest a viable workaround until the issue is resolved? This is a show-stopper for customers that rely on CI/CD tooling for MI deployments.
How is that a usable cloud architecture?
Microsoft break our Dev/Test/Prod pipelines and we are meant to wait until sometime in mid-April for the SSDT projects to work again?
Does anyone know if AWS pulls this kind of trick (I wanted to say a lot more there, believe you and me) ?
I am meant to demo this to senior members of our company to show we have an auditable DevOps process, but you've just made it look like amateur-hour at best.
Can you tell me which product team broke our software that we pay good money for?
Thanks
Jonathan
**Update on the issue. **
@Thomas Totter
@AreHH , anonymous user, @JUMARIE Fabrice , @Butler Jonathan
@Dan Guzman
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 to affected customers. 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
With regards to schema compare issues, someone has proposed a workaround using Azure Data Studio:
https://learn.microsoft.com/en-us/answers/questions/783680/is-sql-managed-instance-no-longer-compatible-with.html
Hello
Have you tested this with pulling changes into and out of Visual Studio SSDT projects? (plus the commit cycle)
Thanks
Jonathan
I've tried, but couldn't figure it out.
@Thomas Totter , @Butler Jonathan , @JUMARIE Fabrice , anonymous user, @AreHH , @JUMARIE Fabrice , @Dan Guzman
Latest Update on the issue.
VS 2019 users should upgrade to 16.11.15 https://learn.microsoft.com/en-us/visualstudio/releases/2019/release-notes#16.11.15
VS 2022 users should upgrade to a minimum of 17.2.0 https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes#from-developer-community-3
Regards,
Oury
Thanks for letting us know.
As a point to note, anyone using Visual Studio 2019 for SSDT projects would have had to upgrade to VS2022 or create a new development machine (or VM) in order to keep working and not just for a few days but actually for months.
I don't think I can impress on Microsoft enough the cost, risk and damage to reputation for reliability they are introducing to the development platform with this breaking change to Managed Instance. Then also the removal of Managed Instance remediation without any notice whatsoever, apparently because MS had only released a fix in VS 2022.
We now know we cannot trust Visual Studio to work with certainty for any given period with Azure cloud products.
Lesson learned.
Thanks
Jonathan