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. Implement FILESTREAM for blobs into Azure Blob Store

    Storing blobs in the database is fairly pointless when you have a dedicated blob store. Implement the FILESTREAM protocol to store blobs in a user's azure storage

    845 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    17 comments  ·  Flag idea as inappropriate…  ·  Admin →

  2. PolyBase: Support for Azure SQL Database

    Azure SQL Database does not currently support Polybase, though it is supported in the on-premise version.

    663 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    26 comments  ·  Flag idea as inappropriate…  ·  Admin →

  3. Add Master Data Services (MDS) to Azure hosted MS SQL.

    Add Master Data Services (MDS) to Azure hosted MS SQL.

    546 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    32 comments  ·  Flag idea as inappropriate…  ·  Admin →

  4. Traffic Manager for SQL Database

    The traffic manager is a great way to account for failover between web nodes in different data centers. However, an analogous paradigm doesn't exist for databases. In the premium tier, you can enable active geo-replication. However, all applications dependent on the primary either need to have their connection strings changed over when failing over between data centers, or they have to have some sophisticated retry logic built in at the application tier. It would be great if applications could point to a single, consistent endpoint and the geo-failover could be handled at a higher level the way it is with…

    294 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

  5. allow database to reside in different resource group to server

    Currently, SQL server databases must be created in the same resource group as the server. It would be great to allow databases to be created in different resource groups. This would allow full environments to be created and destroyed while leveraging elastic pools.

    260 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    unplanned  ·  8 comments  ·  Flag idea as inappropriate…  ·  Admin →

  6. Bring SQL Databases (MS SQL Database as a Service) to Azure Stack

    When is comes to app development on PaaS platforms, Databases and DBaaS are "core" & "can't-live-without".

    I see them already included in first release ;)

    242 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    unplanned  ·  9 comments  ·  Flag idea as inappropriate…  ·  Admin →

  7. Allow the USE statement to switch between databases on the same Azure SQL Server

    We use different databases on the same SQL Server as part of a solution and the limitation of not being able to run USE <database> limits us to Azure SQL VMs only instead of using Azure SQL Server.

    Per Azure Documentation:

    USE statement: To change the database context to a different database you must make a new connection to the new database.

    Seems that there should be a way to overcome this limitation. Help us, Microsoft, you are only hope!

    239 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →

  8. Support staging/production scenario as in Windows Azure

    This could be done with the future cloning technique or perhaps a more sophisticated one?

    193 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →

  9. Allow using Query Notifications with Azure SQL Databases

    Please allow using Query Notifications with Azure SQL Databases.
    In combination with OutputCache having SqlDependency set the Query Notifications mechanism should reduce web sites load and increase pages response time.

    178 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →

  10. Grant access to Azure DB via host name (reverse DNS) instead of IP address

    Clients behind dynamic IP addresses are unable to make use of Azure DB for desktop and server application because I cannot know the IP address that their workstations might be calling from.
    I can use DynDNS to maintain their external host name but good luck to anyone who wants to use DB sync or to direct access the Azure DB databases in this type of environment.

    Static IP is not available to many of our clients as they are in remote locations that only have 3G/4G coverage

    143 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →

  11. Support for DML operations with external tables in Azure

    I've seen it around in a few places that this might be something that's in the works. Is that certain, and is there an ETA on its release? The elastic database queries are a huge improvement, but our application would benefit greatly from write access as well.

    139 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    11 comments  ·  Flag idea as inappropriate…  ·  Admin →

  12. Azure Sql database password force change on first login

    Azure SQL Database needs a feature, like SQL Server, to enforce password expiration, and MUST_CHANGE for SQL Logins

    90 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

  13. Master Data Services (MDS) configured to Azure SQL.

    Master Data Services (MDS) currently does not support having Azure SQL DB as it Data source. We have entity store on PaaS and MDS on IaaS and we want to MDS to be configured to Azure SQL instead of on-prem SQL.
    Or even better to have MDS as PaaS.

    74 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

  14. One click subscribe to notifications when long running task completes

    When you initiate a long running task, such as changing SQL Azure service levels from standard to premium, upgrading a SQL Azure server to V12, etc., anything that could potentially take hours, you should be able to receive an email notification of when that task completes. On the notification panel you see when the task initiates. There could be a 'subscribe' button next to the running task that means you will be notified via email when it completes. I hate having to keep coming back to check on a long running task and this would make things a lot more…

    8 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    unplanned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →

  15. Prevent refresh by hitting F5 in the Azure Web Portal when typing

    There are a few interfaces in the portal where you can type queries: SQL Editor, Azure Data Explorer, Azure Cloud Shell... Unfortunately, you may hit F5 and lose everything. Please prevent it!

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

  16. SqlBulkCopy.WriteToServer fails on SQL Azure if destination table is temporary

    SqlBulkCopy.WriteToServer fails on SQL Azure if destination table is temporary.

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    unplanned  ·  AdminMicrosoft SQL Server (Product Manager, Microsoft Azure) responded

    Upvotes: 30

    <=-=Oct 25 2011 2:38PM=-=>

    Hi Andrey,

    Thanks for reporting this issue. SqlBulkCopy.WriteToServer does not work in this case because SQL Azure currently does not support temp table. We will route this bug to SQL Azure team so that they can follow up with you.

    Young Gah Kim
    Development Lead
    ADO.NET Managed Providers and DataSet Team

    <=-=Apr 19 2012 6:15PM=-=>

    Hello Andrey,
    Thanks for reporting the issue. The problem is due to the fact that SQL Azure doesn’t support 3-part names for stored procedure calls. In this case, the driver/provider use tempdb.sys.sp_* syntax to access certain stored procedures that provide metadata about objects and these calls fail. We are looking at resolving the issue & enabling 3-part names for tempdb calls.
    Otherwise, you can use temporary tables in SQL Azure fine – we do support it with the restriction mentioned above. Additionally, you can’t create temporary tables…

  • Don't see your idea?

SQL Database

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice