Skip to content

Settings and activity

2 results found

  1. 282 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    under review  ·  Kendra responded

    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.

    Anonymous shared this idea  · 
  2. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    I agree. This has been a significant challenge for our organization to have to run a profiler trace just to find the failing statement. It slows down the troubleshooting process.