Settings and activity
15 results found
-
1 voteAlex supported this idea ·Alex shared this idea ·
-
8 votes
Thanks for the suggestion!
We’re actively reviewing this suggestion alongside some others for Tab History. We’ll update again here when we progress.
Alex supported this idea · -
17 votes
The team are currently reprioritising this suggestion with a view to picking it up during 2019.
Alex supported this idea · -
17 votesAlex supported this idea ·
-
20 votesAlex supported this idea ·
-
24 votesAlex supported this idea ·
-
22 votesAlex supported this idea ·
-
30 votesAlex supported this idea ·
-
35 votesAlex supported this idea ·
-
32 votesAlex supported this idea ·
-
41 votesAlex supported this idea ·
-
71 votesAlex supported this idea ·
-
75 votesAlex supported this idea ·
-
92 votesAlex supported this idea ·
-
285 votes
Thanks to everyone for submitting feedback on this in the form of both voting and comments.
Currently, SQL Source Control does not have strong support for Azure SQL Database: as folks have noted in this item, AAD support, particularly with multi-factor authentication, is desired. Currently SQL Source Control does not work at all with Azure SQL Database with MFA enabled.
An additional issue worth mentioning is that pains with SQL Source Control performance may be worse than interacting with Azure SQL Database due to latency.
We would like to improve the user experience and support for Azure SQL Database, and doing so almost certainly involves addressing both of these issues. This is an area we are beginning to investigate more fully.
Alex supported this idea ·