SQL Managed Instance

  1. Support DNS aliasing of an Azure SQL Managed Instance (at least for public endpoint)

    As it is already supported for Azure single SQL Database, it would be nice to be able to create an alias for the Managed Instance, especially for the public endpoint address. All clients connecting directly to the public endpoint would be able to use an alias instead of the real name of the instance. Switching instances, disaster recovery, migration scenarios would be a lot easier to handle.
    FYI, creating a public CNAME record redirecting to the public endpoint address of an MI (like instancename.public.***.database.windows.net) does NOT work : IP resolution is good, but no way to login to the instance…

    68 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Azure SQL PiTR - Option to disable or set to 1 day retention

    We currently have an SQL managed database, which we use for development purposes.

    We are developing how our data ingest will work, currently we drop the tables every day, and re-load all the data. As of the 31-AUG we started getting charged for PiTR which we didn't know about, until PiTR started costing us upwards of $120 per day.

    What I found out is after the initial backup (free) any changes were replicated to 6 regions (GRS storage) and set to 35 days retention period. These are backups we don't want or need, as data is ingested from the Datalake.…

    36 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Incorrect message about valid values for compatibility level

    On a Managed Instance v12.0.2000.8, run an ALTER DATABASE for an invalid compatibility_level, like this:

    ALTER DATABASE [StackOverflow2010] SET COMPATIBILITY_LEVEL = 150

    And the message comes back saying:

    Msg 33528, Level 16, State 1, Line 3
    Valid values of the database compatibility level are 100, 110, 120, or 130.

    That's not true - 140 is also a valid value for the compatibility level.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

SQL Managed Instance

Categories

Feedback and Knowledge Base