SQL Managed Instance

  1. Make smaller instance sizes available

    It wouldd be great to have smaller instance sizes available - or even a 'basic' tier. this is blocking the route to PaaS at the moment. Most of our customers run on 4/6 cpu cores at most, so cost-wise managed instance is way beyond what is justifiable. Also, its expensive to test. A basic tier would be really useful for POC;s.

    100 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 →
  2. Support regional settings to fix GetDate() function

    GetDate still on UTC all the time. For the promised value of MI to be the destination for lift&shift without code changes, this breaks it. Now developers have to review their code and update it for MI and if decided to move the database to their IaaS environment, they have to change it back again.

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

    We’ll send you updates on this idea

    14 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.…

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

    We’ll send you updates on this idea

    15 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are pleased to announce that this feature has now been completed and generally available (GA) for Azure SQL Managed Instance.

    Setting PITR backup retention period for active databases from 1-35 days is now possible using Azure Portal and PowerShell, and setting backup retention period for deleted databases from 0-35 days is now possible using PowerShell only.

    Official documentation page: https://docs.microsoft.com/en-us/azure/azure-sql/database/automated-backups-overview?tabs=managed-instance#change-the-pitr-backup-retention-period-by-using-the-azure-portal

    How-to blogpost: https://aka.ms/mi-backup-tuning

    Thank you for your feedback, please keep it coming.

    Azure SQL Managed Instance product group

  4. Azure Managed Instance must suport all Collations

    Azure Managed Instance must suport all Collations, not just SQLLatin1GeneralCP1CI_AS Collation

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

    We’ll send you updates on this idea

    completed  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow for a Managed Instance to have a public endpoint

    It'd be great if this could happen. The idea of integrating an MI with other Azure services via additional virtual machines using on-prem data gateways and self-hosted integration runtimes is not ideal.

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

    We’ll send you updates on this idea

    12 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Azure AD Administrator to include all sysadmin privileges

    Having set an Azure AD Administrator account which is an AD Security group. I would like to have functionality included which will allow members to have effectively sysadmin privileges. The whole thought on this would be to allow the AD Admin account the ability to perform more of the day to day DBA activities on all databases.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Metric Alerts

    SQL Manged Instance needs to support the same Metric Alerts that SQL Database has.
    This is essential to being able to monitor SQL Managed Instance as part of the cohesive alerting setup as our other Azure resources.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Change Data Capture (CDC)

    Please enable Change Data Capture in Azure SQL.
    Very important feature that allows tracking version info about DB tables.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for voting for Change Data Capture feature in the Azure SQL DB Managed Instance. it’s been available in SQL MI since its beginning, so you probably wanted to vote for it in other deployment options of Azure SQL DB – single database and elastic pools.
    Please condsider using CDC in SQL MI, or vote for adding CDC to the rest of Azure SQL here: https://feedback.azure.com/forums/217321-sql-database/suggestions/9256023-change-data-capture

  9. Provide Option to "Restore a Deleted Database" - the same functionality which is avaialbe in Azure SQL Databases

    Like Azure SQL Databases, provide the option to restore a deleted database in Azure SQL Managed Instance using the portal.

    THe present work-around https://blogs.msdn.microsoft.com/sqlserverstorageengine/2019/01/21/recreate-dropped-database-on-azure-sql-managed-instance/ isn't exactly easy, particularly as SQL DBAs in the organisation I work for , do not have the permissions to do this in the Azure Portal. Furthermore, in the event of an accidental drop; which is quite easy to do in SSMS, including V18.0, the drop confirmation box is not always displayed.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. I want to rename DB

    I want to change the DB name after restoring the DB and restoring the DB name in order to use the restored DB as the production database.
    If the DB name can not be changed, there is a possibility that it is necessary to change the connection string after the DB restore.

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

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. "ALTER DATABASE <db name> ADD FILE <logical file name>" doesn't work under specific condition in Managed Instance

    I restored to Managed Instance via ".bak" file. this source DB configured some database file.

    After restored, I executed
    "ALTER DATABASE <db name> ADD FILE <logical file name>",
    following error occured.


    Unable to open the physical file "https://wasd2p.blob.core.windows.net/managedserver-071/data/829f3544-***_3.ndf". Operating system error 80: "80(The file exists.)".

    (if source DB's database file is single, work correctly.)

    execute this T-SQL with changing "logical file name",
    physical file name's seq number in error message incremented
    and finally, it worked.

    is this bug ?

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

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Approval time for Managed Instance preview

    How long should we expect to wait for approval to participate in the preview. I accepted preview terms two weeks ago and requested an April start. Now we're anxious to kick the tires.

    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 →
  13. Support a DR (Disaster Recovery) solution with Azure Backup / Geo-Replication

    Currently I was only able to get SQL MI accepted by a client because for the DR scenario I was able to manually script client initiated backups that backup to geo-replicated blob storage.

    SQL MI does support replication to a secondary site but this makes it too expensive for most clients. But they must have a DR solution as the 7-day point-in-time locally redundant backup doesn't meet their security requrement.

    1 vote
    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 →
  14. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Why not autocreate route tables when creating a virtual network?

    The page https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-vnet-configuration describes a 4 step process

    First. Create a Virtual Network Instance

    Second. Create a routing table

    Third. Add an 0.0.0.0/0 Next Hop Internet route to the table

    Fourth: Associate this route with the Virtual Network

    That is a lot of friction - why not offer the ability to have steps 2-4 automatically occur?

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

SQL Managed Instance

Categories

Feedback and Knowledge Base