SQL Database

How can we improve Azure SQL Database?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. 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.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. New Pricing Tiers - X Small Databases

    I think current Basic Elastic 50 and Single Database are still expensive for small databases, currently I have got 7 databases, size together 200MB. How can be the Basic for ~$74.40/mo and pool 5GB good for this?

    Currently I am paying them as Single Databases but it is also expensive as my databases will never get 2GB.

    You could create additional Tiers for Single Databases of max size 100MB and 500MB and Elastic Pool could be indeed also 1GB or 2 GB.

    Similar requests were closed as Completed

    https://feedback.azure.com/forums/217321-sql-database/suggestions/4908333-sql-azure-more-scalable-pricing-for-multiple-smal

    https://feedback.azure.com/forums/217321-sql-database/suggestions/9908991-add-extra-small-elastic-database-pool

    I can see the advantage of Basic 50 Elastic Pool…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Bug: DDL Triggers are NOT disabled during Bacpac import

    During the import of a Bacpac DDL triggers are not disabled and therefore are fired on each trigger defined DDL operation as they are carried out during the import process.

    An example of this is a trigger firing on ALTER TABLE actions, where the import process is recorded by the trigger in an audit table. However when the contents of the audit table itself is attempted to be imported a duplicate primary key error is thrown as the import process has already written rows to the table.

    As an example:
    Create a DDL trigger using the attached text file on…

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. No DTU metrics can choose in Azure Monitor Alert

    One of our customer is concerned about the retirement of Classic Alert next year.
    They want to use DTU metircs as criteria but there's no DTU related metircs in Azure Monitor Alert.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Granular data masking management on rule-level

    Provide more granular management of Dynamic Data Masking.

    This would allow admins to exclude SQL users for a specific masking rule instead of excluding them for the complete masking rule set.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Azure database export fails when split_string is involved

    Database compatabilty level 130.

    Repro steps:

    alter function dbo.tt
    (@id varchar(max))
    returns table
    return
    select
    * from
    dbo.string_split(@id,',') t
    inner join
    dbo.numbers n
    on n.id=t.value

    Export dacpac fails stating unresolved reference split_string,while the function itself works

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  7. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Provide SQL Server Connector functionality for Azure SQL PaaS

    In order for an EKM provider to communicate with an Azure Key Vault the database must be either Azure SQL IaaS or an on-prem instance of SQL Server. When using Azure SQL Paas, however, it would be great to have this level of security available as well as the ability to manage credentials in one area and within a Key Vault.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Faster scaling between service tiers/performance levels

    Current database scaling can be slow..
    Azure SQL Data Warehouse features the ability to scale between performance levels within seconds. It should also be an aim of Azure SQL DB to also offer scaling within seconds/small number of minutes. Key to this is presumably eliminating the data copying that goes on during scaling.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Transparent Data Encryption Support for ARM template

    Currently, we still cannot enable Transparent Data Encryption Through ARM Template. Please implement this feature, because it would be really helpful for users.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. sp_msforeachdb for Azure Database

    SQL Server 2008 through 2016 had this undocumented stored procedure which allowed the DBA's to execute a certain task/script on multiple database at one shot but with Azure database/logical server this stored procedure is no more available.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow the user to disable int/bigint identity 1000/10000 increase

    Reference: https://www.jitbit.com/alexblog/239-sql-server-bug-ms-calls-a-feature/

    Currently, the next identity value jumps automatically whenever the SQL server instance restarts. Most of us don't want that jump to happen because it'll leave thousands of unused ID numbers behind. You can only fix this problem by specifying the -T272 startup parameter for SQL Server which is not available to us Azure SQL users.

    Please let us disable this "feature" easily.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Blob Auditing Type for Azure SQL Database Threat Detection

    Blob auditing was recently rolled out for Azure SQL Database, "which provides higher performance, supports higher granularity object-level auditing, and is more cost effective." However, Threat Detection does not currently support blob auditing, only table auditing. As a result, one of the most common reasons to turn on auditing, threat detection, cannot actually use the better performing method. Please allow Threat Detection to use blob auditing types.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Regarding Alerts - Want to notify whenever login fails anytime

    Alerts can be set to notify login failure but it only be set per user database, not server or 'master'.
    For strict security measures, I hope it sends an alert mail of login failure in spite of destination database.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. quality

    Data Quality capabilities allow the user to profile and cleanse their data in Azure based on commonly used Data Quality Standards (dimensions) such as Completeness, Uniqueness, Consistency, Conformity, Validity, and Accuracy.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Elastic pools, ability to configure minimum eDTU per database singularly

    My request is to have the possibility to setup for each database, singularly, the minimum eDTU available.

    At the moment it's possible to set a maximum and a minimum for all databases.

    I think, for the nature of this kind of services, it's crucial to allow to maybe setup 0 as minimum for databases you do not care (eg: testing-staging instances, new projects) and a higher minimum to the more significant ones.

    Maximum will be interesting as well, but minimum i think is more important to guarantee a quality of service.

    In little elastic pools, it's easy be over the…

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow database specific alerts to be set up at elastic pool level

    At present, you can set up alerts for elastic pool resources and alerts for individual database resources. However, if you have say 100 databases in your elastic pool, setting alerts per database is a real pain.

    It would be good to set up database specific alerts at elastic pool level so it can be managed easily.

    For example, we'd like to set up an alert when the number of database sessions reaches 80% but doing this across all of the databases in an elastic pool isn't easy.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Provide a way to force "transient" SQL errors for testing.

    When using Azure SQL, transient errors due to throttling, load balancing etc become a fact of life quickly. There are methods to deal with this, but testing that the methods actually work in your server is very tricky or impossible.
    It would be great if there were a way in the portal, or Powershell APIs, to force transient errors in some way. For example, "for the next N minutes return a throttling error for every second operation".
    For examples of the lengths developers go to in order to test this:
    https://github.com/robdmoore/SQLAzureTransientDemo
    http://www.asp.net/mvc/overview/getting-started/getting-started-with-ef-using-mvc/connection-resiliency-and-command-interception-with-the-entity-framework-in-an-asp-net-mvc-application

    this is a great deal of tricky code…

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Bring back T-SQL debugger (and make it work with MI)

    The T-SQL debugger, while not perfect, was a very useful tool for me. We've recently migrated a large database with some complex SPs from MySQL to an Azure Managed Instance, and while the debugger did not work with the MI, it did work with our on-prem dev server. Using the debugger has made it so much easier to track down where something has gone awry. I was very disappointed to learn that it's being removed completely in SSMS 18.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Implement password expiry & password history & certain number of account lockout for Azure SQL databases

    We could see below gaps for Azure SQL Database (for PAAS scenario)

    1) There is no Password History
    2) There is no Password Expiry
    3) There is no Account Lockout set (wherein account will be locked out after certain number of failed attempts) which could lead to bruteforce attacks.

    All these above parameters must be addressed and aligned in accordance with Industry Standard.

    As discussed with Omeswar Reddy Danwada uploading this idea

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

SQL Database

Feedback and Knowledge Base