SQL Database

  1. Keep Azure SQL Premium RS

    Microsoft should reconsider retiring the Premium RS tier of Azure SQL. It provides a service for companies like ours that want to host their QA/Staging environments in Azure but don't need the full reliability of the Premium tier. None of your other offerings will work for us. We make use of In-Memory tables (OLTP). This option is only available in the Premium/Business Critical tiers. Both of which are too expensive for QA/Staging environments. To retire this option without providing anything of comparable value is a mistake. How can customers feel confident in moving their applications to the cloud if Microsoft…

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Navigating away from "Configure" blade of Azure SQL DB always prompts that unsaved edits will be lost

    If you click on the Configure item to launch the configure blade in the Azure Portal for Azure SQL DB, it will always prompt you to discard changes despite no changes not being made. This is obviously incorrect and confusing to inexperienced (or unprepared) users.

    Please change this to only flag if unsaved changes are actually made.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. Authentication method when connecting

    Authentication method when connecting

    Requests the addition of the ability to turn off SQL Server authentication.
    For security reasons, the goal is to turn on only Azure AD authentication connections.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support update of backup retention days via the azure cli

    The Azure CLI for SQL MI instances does not support update of the backup retention time. The documentation does not seem to refer to such an option, leaving only powershell and the REST APIs as options.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. Instant Zero-Copy Clones of entire database or single tables

    If you want to differentiate from AWS, then it is better to stop comparing prices, and think about data management. Customers need a quick way to test production DBs without having to wait for hours to create a copy. So, just provide a facility to do instantaneous zero-copy clones of entire databases in a second. Or to go even further, provide a way to instantly clone single tables. It is not that hard to actually build this, and I bet this will give Azure SQL a significant advantage in the market place. Happy to give you more data management ideas…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Remove sql server admin requirement on Import database

    Prior to deleting a database, we create a bacpac and export it to an Azure storage account, this is so that at any time in the future we can restore the database from the backup.

    It is a huge security hole to provide our support team with the sql server admin password to enable them to restore the database.

    Please remove this requirement when importing a database.

    We cannot use the Active Directory authentication type as we have 2FA enabled on all our accounts.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Replication: Error when publishing from SQL 2017 to Azure - "Azure server is older version of SQL Server"!

    When setting up replication from an on-prem SQL Server to Azure SQL MI, an error is produced when setting up a publisher on-prem: "Server x is an older version of SQL Server and cannot be the Distributor for server y". At a guess, this is probably due to versioning number changes with the cloud version of SQL (2017 is v14, while Azure SQL is v12)

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  8. Round-robin read replicas and provide performance metrics of replicas in portal

    There is more than one read-replica and it would be a huge performance benefit to be able to round-robin the connection to them. Would also be great to get visibility into the replicas via the Azure portal.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. PITR Restore is not showing in the Portal after database restore

    A customer recovered a deleted Azure SQL DB replacing old one. Then he wanted to restore again to previous point in time he should have more than 7 days of backup, however it was not showing in the Portal. Only was able to restore to previous restore point using Powershell.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  10. Azure SQL Threat Detection Filters IP from Azure SQL Query Editor

    Today we received an alert as "An unfamiliar principal successfully logged on to server [SERVERNAME]" with some following details:

    Client IP address: 23.96.227.***

    Client IP location: Chicago, United States

    Data center: North Central US

    Client application: Azure SQL Query Editor

    After working with MS Support Technician, it turns out that Detection Threats doesn't recognize internal IP from a server node assigned by Azure SQL Query Editor.

    This alert created huge pressure and noise in order to identify the origin of this connection.

    It is great if any IP from Azure internal nodes are whitelisted by Threat Detection.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. SQL Azure maintanance work should be re-scheduled as per our prefered time

    Most of the time our service was down because of DB maintenance work. So, we need our preferred time to set DB maintenance work.Please consider and update us.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Backups

    Currently, a user account with the appropriate permissions could delete all of the LTR backups and then delete the sql server and at that point the database and all backups would be instantly and permanently gone and could not be recovered either by the client or by Microsoft. This seems like a large concern for anyone using Azure Sql database in a production capacity. There needs to be some type of immutable storage option for PITR and LTR backups. If one account were to be compromised this scenario could occur. Either allow directing backups to a storage account where immutable…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Fix quality of daily cost data visibility

    On various days / weeks there are gaps in cost data for various resources. This tends to self-heal after up to 1 week (incl. history correction). All custom control / alerting which looks on anomalies in cost trends fail due to this; we also loose opportunity to act quickly on unexpected cost raises due to changes, testing activity or unplanned activity on prod - it's critical to see this data at least with daily delay, ideally near real-time.

    Examples of incidents: on Dec 8-9 we stopped getting cost data for any of our SQL DWs, SQL DBs or PostgreSQL DBs…

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  14. Be able to set ApplicationIntent in external data sources

    Enable Application Intent in External Data Sources. Azure External Data Sources cannot take advantage of Read Only replicas, even if accessed from a read only replica. The external data source has no way of signaling the Application Intent to the traffic manager. Thus they always point to the read write replica, regardless of how the client is configured.

    77 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Vulnerability Assessment - allow periodic recurring scans without requiring email address for results

    Currently, enabling Azure SQL Advanced Data Security -> Vulnerability Assessment -> Periodic recurring scans at the server level requires an email address be provided so database scan results can be emailed.

    Would like to see an option for emailing scan results rather than requiring scan results be emailed after each scan, and/or allow the "Send scan reports to" field to be left blank.

    This benefits situations where vulnerability-related information cannot be sent over email.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Enable simple OData endpoints for SQL Azure Database

    Something like this used to exist as part of SQL Azure Labs (https://azure.microsoft.com/en-us/blog/introduction-to-open-data-protocol-odata-and-sql-azure/) but was not taken to GA, and has been discontinued.
    I'm looking for the ability to:
    * single-checkbox "enable" a SQL Azure Database as an OData service
    * additionally checkbox "enable" it's contents by schema, table, and/or view for read, write, update and/or delete access
    * possibly configure the above access per user, or tie it into existing access control per object

    Since this capability does not exist, I am researching creating my own endpoint (which requires coding and a separate VM to run a…

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Please add details in Activity Logs (Firewall enable)

    There was a situation that we don't able to login to our database. We investigated and found out that the Firewall settings (Allow Access to Azure Services) of that database has been turned-OFF. So we turned it ON. we don't know who turned OFF the switch. So we go to the Activity Logs, and we see who are the people who touch the settings but unable to determine who turned-OFF or ON since there are no word "ON" "OFF" in the activity logs. Can you include this to the Activity Logs? for us to determine who actually turned-OFF or ON…

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  18. [Bug] Unable to add firewall rule failed with irrelevant chinese error message in China Azure Cloud.

    无法重写服务器 gbsintern 的防火墙规则和刷新刀片式服务器。
    错误代码: undefined
    错误消息: An unexpected error occured while processing the request. Tracking ID: 'eb8923ca-62bc-4837-9e34-501eb4c1b654'

    But I got error message below with azure cli.

    Operation failed with status: 'Conflict'. Details: Windows Azure SQL Database supports a maximum of 128 firewall rules.

    If i delete one old rule , i can add new rule.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. The operation has been cancelled by user

    subnet we are able to destroy without removing all references which can cause multiple issues. like if we have added firewall rule in sql server which can cause issues like new subnet we can't add in firewall rule.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Monitor queries on secondary database when read scale out is enabled in Premium tier

    Monitor queries on secondary database when read scale out is enabled in Premium tier. Currently we can only find out if query is getting executed on secondary database by using SELECT DATABASEPROPERTYEX(DB_NAME(), 'Updateability') but there is no way to identify in Query Performance Insights.

    188 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

SQL Database

Categories

Feedback and Knowledge Base