This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(96, 22%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETE%3C/text%3E%3C/svg%3E)
As of the last few days, I am no longer able to do SQL schema compare for a database in SQL Managed Instance in Visual Studio using SQL Server Data Tools. This was working last week but now I get the error "Source is unavailable: dbname". After manually editing the .scmp file to tweak the connection string, I get a slightly different error "unable to determine database platform type". When I setup the source/destination connection it can connect to the SQL Managed instance OK using Azure AD - I know this because I get a list of databases in the "Default database" dropdown. However, when I click the "Compare" button to do the actual compare I get the error.
This functionality is still working when connecting to Azure SQL Database, but not Azure SQL Managed Instance. Is the latest SQL Managed instance version (Microsoft SQL Azure (RTM) - 12.0.2000.8 Feb 25 2022 16:04:35)) no longer compatible with SSDT?
@Tim Eldridge , what values does your MI return for SELECT SERVERPROPERTY(N'Edition'), SERVERPROPERTY(N'EngineEdition');?
Edition = "SQL Azure" and EngineEdition = 8
I captured these queries at the start of SSDT schema compare so I was curious as to whether something changed as a result of the upgrade.
SELECT CASE WHEN SERVERPROPERTY(N'Edition') In ('SQL Data Services', 'SQL Azure') OR SERVERPROPERTY(N'EngineEdition') In (5, 6) THEN 'true' ELSE 'false' END
go
SELECT CASE WHEN SERVERPROPERTY(N'EngineEdition') = 6 THEN 'true' ELSE 'false' END
go
![](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(163.2, 84%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYM%3C/text%3E%3C/svg%3E)
In general, this situation is caused by a mismatch in SQL Server version, there's no SSDT standalone installer for Visual Studio , try to upgrade VS with SQL Tools extension
![](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(316.8, 28.000000000000004%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJZ%3C/text%3E%3C/svg%3E)
We have the same issue on VS 2019 with SSDT 16.0.62111.25150
Hello
Same problem, SSDT Schema Compare working OK previously now cannot connect to Managed Instances, On-Prem is OK (SQL 2016-2019).
Is this helping us transition to the cloud? No
Does this increase risk of failure if we cannot develop for cloud database? Certainly, YES.
Should the interface provide feedback when the connections aren't working properly? YES.
(upload image not working, drag & drop or upload)
After clicking Schema Compare -> select target -> select connection; sometimes the databases will list from the MI other times they won't, in either case the dialogue remains greyed out as if the connection has failed. If a previously connection to another server is listed that one is used in the dialogue and not the instance chosen (but failed silently).
This needs to be and must be better.
We can't have our development projects crippled by functionality failing because the cloud has been updated.
How about some info in the Visual Studio window if VS does need updating (trying that next - not trivial when I have to create update images first because it's so large to distribute!).
Thanks
Jonathan
Hello YufeiShao-MSFT
Please see my comment below regarding this functionality break for SSDT (due to cloud update?).
Do I need to raise a Microsoft support call for a resolution response time, i.e. is this a MI fix or SSDT fix (don't hold your breath).
This is a breaking [change] for our environment and deployment pipeline process.
Please could you offer guidance/reassurance/help to fix and timings?
Thanks
Jonathan
Hello YufeiShao-MSFT
I installed VS 2022 community edition with the latest version of SQL Server data tools yesterday and the issue still occurs. I agree with ButlerJonathan-2222 - this has broken development and deployment processes for a large number of people/teams and it needs an urgent fix. I think the fix is an update to SSDT to support the latest version of SQL MI
Thanks
Tim
This is a feedback site with suggestions for submitting questions:https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0
You have got to be joking.
Microsoft break Visual Studio SSDT projects as a development pipeline and you want us to ask for the feature returning?
I think the cat is out of the bag. Microsoft is not a reliable partner. I'm now looking at other products and tooling where support is a priority.
I haven't heard back from the support call yet but I'll update here and on the feedback I raised through VS yesterday (link below to upvote).
Utter shambles and a disgraceful response so far.
Upvote the feedback to get some action on this utter shambles: https://developercommunity.visualstudio.com/t/Is-SSDT-Schema-Compare-broken-for-Azure/1702437
Thanks
Jonathan
Also, can as many people who are able to, please upvote this issue (please all who are following the problem? we are at 14 votes with 32 following updates).
Many Thanks
![](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(262.40000000000003, 53%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVH%3C/text%3E%3C/svg%3E)
I have raised a ticket with MS. This was the response:
I have looked internally and realized that new version of MI (code package 16.0.41.326) is making it impossible for customers to use SSDT/Visual Studio with their managed instances. However rest assured, PG teams from Visual Studio and Managed Instances are working on the fix. Changes will first become widely available to our customers in VS 17.2 preview 3, which is scheduled to release on April 12th.
In the meantime, a quick workaround is to downgrade the MI version and then test it, for which I am now raising a case with our Product team and let you know on the progress soon.
I'm still waiting on the rollback and currently on versions :
SQL Azure 8
Microsoft Visual Studio Enterprise 2019: Version 16.7.3
SQL Server Data Tools 16.0.62008.03130
![](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(246.4, 0%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHV%3C/text%3E%3C/svg%3E)
Any idea when this will be fixed? Releasing our SQL database is becoming incredibly difficult now.
after the roll back on managed instance i can now confirm SSDT Schema compare is working again. MS confirmed a new release of SSDT is required (no ETA yet)
I would suggest to create a support ticket if you want to have this fixed prior to release of a new version of SSDT
Hi
The short answer is that if you want to get Visual Studio working (Server Explorer, SSDT) with the Managed Instances then you need to raise a support call.
The fix is supposed to be released in VS 2022 17.3 available here - i haven't tried it yet.
But i need 2019.......can't find any update to that yet..
https://learn.microsoft.com/en-gb/visualstudio/releases/2022/release-notes#17.1.3
Good luck.......with Microsoft you'll need it.
JB
feedback from ticket on the ETA:
I have checked with PG about the ETA on the fix and they mentioned that VS update with a fix should be released on April 12th.
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
![](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(105.60000000000001, 8%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIE%3C/text%3E%3C/svg%3E)
![](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(211.20000000000002, 74%, 30%)' 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)
THANKS
The problem is now resolved for me!
I have installed Visual Studio 2019 community edition, enabled preview features and schema compares are now fully functional again. Full details of my VS 2019 version are shown below:
Microsoft Visual Studio Community 2022 (64-bit) - Preview
Version 17.3.0 Preview 1.0
![](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(278.4, 27%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Also now working for me using Visual Studio 2022 Version 17.2.2
![](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(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
I am not having that issue with SSDT. Please verify you are using the current version of SSDT.
Mine is:
SQL Server Data Tools 16.0.62111.25150
Running on
Microsoft Visual Studio Professional 2019
Version 16.11.10
I am using the most up to date version of SSDT as I downloaded it yesterday. My Visual Studio 2019 is also up to date, more detail below:
Visual Studio professional 2019
Version 16.11.11
SQL Server Data Tools 16.0.62201.17150
This wasn't an issue last week, I could do schema compares with SQL MI in this version of Visual Studio as well as Visual Studio 2017 and have been doing this for almost a year now. However since the last update was applied to my SQL MI on Fri 18/03/2022 this has stopped working.
@Tom Phillips , so your SSDT is working against MI? What does your SELECT SERVERPROPERTY(N'ProductVersion'); return for you? Given a new SSDT version for VS has not been released as of now, my assumption is the latest MI update must have broken the SSDT platform check. Tools like SSDT need to be aligned (or ahead of) Azure offerings and it seems this was a miss.
From your query I get 12.0.2000.8. and EngineEdition = 8.
I see I am running a slightly older version of SSDT than the OP. I will see if I can duplicate the issue again. I do not see an error when I run schema compare.
![](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(211.20000000000002, 91%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
Update on the ticket from Microsoft - "The problem has been mitigated". I can now perform a schema compare against a managed instance using Visual Studio....
I still can't. Has your managed instance version updated or did you install an SSDT/VS Update?
![](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(179.20000000000002, 35%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
@Andrew Duckers Can you please elaborate on how you fixed this?
We haven't updated anything locally so the change must have been within the managed instance or Azure, I would also assumed any fix will be applied by Azure region/data centre/zone so it will eventually (rather than immediately) be fixed on all impacted resources.
Hi
Do you know if the version or edition of MI has changed?
BTW our MI's have not yet been updated with the mitigation.
Still waiting to hear back on our support call on the subject.
Thanks for letting us know you are back working, fingers crossed.
Still going to have to look at other tooling, we simply cannot have our pipelines cut-off by this amateur-hour stuff.
Thanks
Hi AndrewDuckers-2265 - are you able to run the query below on our SQL managed instance?
select @@Version