SQL Database

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

    24 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 →
  2. 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.

    24 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 →
  3. 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…

    24 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 →
  4. Deploy SSDT database project with external tables fails

    During the deployment of a SSDT Database Project with external tables on Azure, deployment fails with this error message:
    2018-07-10T17:23:00.8539155Z Dropping [EDS]...
    2018-07-10T17:23:01.7970626Z An error occurred while the batch was being executed.
    2018-07-10T17:23:01.8200128Z Updating database (Failed)
    2018-07-10T17:23:02.1289225Z ##[error]*** Could not deploy package.
    Error SQL72014: .Net SqlClient Data Provider: Msg 33165, Level 16, State 1, Line 1 Cannot drop the external data source 'EDS' because it is used by an external table.
    Error SQL72045: Script execution error. The executed script:
    DROP EXTERNAL DATA SOURCE [EDS];


    • The Target of SQL Project is target platform 'Microsoft Azure SQL Database V12'.

    • A Azure SQL…
    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    23 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 →
  6. 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: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  7. let us pause a sql database

    It would be really nice to be able to pause a sql database, similar to taking one offline in SSMS. It's especially useful if you're moving the DB around to another sub or trying to replace it or something. I don't want to delete the DB that's there...just stop it until I'm confident that I'm finished with it.

    23 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 →
  8. 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…

    23 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 →
  9. 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: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow to query analysis services directly from sql database

    Right now there is no way to combine results from sql and azure analysis services without additional layer of code that would query analysis services and insert results to sql database.

    Before azure we had something called OPENQUERY, that would allow us to query on the specified linked server using syntax that makes sense for that linked server (for example MDX).

    Current implementation of azure elastic query doesn't really help in this situation.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Elastic query without opening firewall to all of Azure

    From the documentation at
    https://docs.microsoft.com/en-us/azure/sql-database/sql-database-elastic-query-vertical-partitioning#best-practices

    It says "Ensure that the elastic query endpoint database has been given access to the remote database by enabling access for Azure Services in its SQL DB firewall configuration"

    There should be a way to enable elastic query without allowing anything in Azure to connect by setting "Allow access to Azure services" to ON.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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…

    22 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 →
  13. 21 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 →
  14. 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: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Azure SQL Database copy operations shouldn't require write access to the source database

    When performing a database copy operation between two different servers it appears that write access is required to both the destination server and the source database.

    See the following error from the Az CLI:

    $ az sql db copy \

    --resource-group source --server source --name source \
    
    --dest-resource-group dest --dest-server dest --elastic-pool dest --dest-name dest

    ERROR: The client '<client>' with object id '<object id>' has permission to perform action 'Microsoft.Sql/servers/databases/write' on scope '/subscriptions/<subscription>/resourceGroups/dest/providers/Microsoft.Sql/servers/dest/databases/dest'; however, it does not have permission to perform action 'Microsoft.Sql/servers/databases/write' on the linked scope(s) '/subscriptions/<subscription>/resourceGroups/source/providers/Microsoft.Sql/servers/source/databases/source'.

    This isn't ideal in use cases where you're automating the copy of…

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

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Send maintenance notification in advance

    Recently we have got maintenance notification one day before maintenance starts.
    It's very useful for me, however, I'd like to get it earlier, e.g. 3 business days before the maintenance.

    20 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 →
  20. Active Geo replication to different subscription

    Customers are looking for this type of feature to replicate data from Prod in UAT/Test. Also to make the database available for third party to separate the costing. Currently custom coding or replication tools are needed, but would be great if the secondary replica can be in another subscription

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

SQL Database

Categories

Feedback and Knowledge Base