SQL Database
-
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
779 votesThis is not currently planned at this time. Will keep this item open for voting and comments.
-
PolyBase: Support for Azure SQL Database
Azure SQL Database does not currently support Polybase, though it is supported in the on-premise version.
470 votesNot planned at this time. Will keep this item open for future review.
-
Add Master Data Services (MDS) to Azure hosted MS SQL.
Add Master Data Services (MDS) to Azure hosted MS SQL.
303 votesThis is not currently planned at this time. Will keep this item open for voting and comments.
-
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…
274 votesThis is not currently planned at this time. Will keep this item open for voting and comments.
-
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 ;)
244 votes -
Support staging/production scenario as in Windows Azure
This could be done with the future cloning technique or perhaps a more sophisticated one?
189 votesThis is not currently planned at this time. Will keep this item open for voting and comments.
-
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!
174 votesThis is not currently planned at this time. Will keep this item open for voting and comments.
-
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.
172 votes -
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.162 votesThis is not currently planned at this time. Will keep this item open for voting and comments.
-
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
124 votesThere are no plans to make this change, but we’ll keep this item open for voting and comments. Thanks
-
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.
89 votesThis is not currently planned at this time. Will keep this item open for voting and comments.
-
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
87 votesAAD supports password expiration. We don’t have plans to do this for SQL logins at this time. We’ll keep this item on the back log, but it is unlikely to be prioritized soon.
-
SqlBulkCopy.WriteToServer fails on SQL Azure if destination table is temporary
SqlBulkCopy.WriteToServer fails on SQL Azure if destination table is temporary.
0 votesUpvotes: 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
<=-=Apr 19 2012 6:15PM=-=>
Development Lead
ADO.NET Managed Providers and DataSet TeamHello 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?