Service Broker should be available in Windows Azure.

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

1. Create a new Database.
2. Check an "Enable OData data services"
3. Get a non-code OData service over the database

Please don't make column store indexes premium only feature. We can use column store in SQL Standard Edition so why here should be different? Premium features should be performance gains to existing features, not banning them altogether for those of us who can't afford the premium prices.

Please enable intellisense on Azure SQL databases. We have had it since SQL server 2008 and seems crazy that it is not available on Azure.

Please add a GUI to manage the users and their privileges in Azure SQL databases.

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

First and foremost: I understand that anyone can spin up a VM and just put postgres (or anything else) on it. This suggestion is not satisfiable by that advice.

What I and countless others would like to see is postgres offered as a 1st class (by Microsoft) database as a service solution.

Right now the only DB could I confidently use on Azure is SQL Server. The third party integration of MySQL by ClearDB leaves a lot to be desired and indeed - it would be better if Microsoft in-housed an option for all the as-a-service DBs, just like RDS.

support is difficult to get and to understand. My databases randomly become unavailable at times with no explanation as to the cause. Just not available and then magically its back up and running.

Why ???

Allow Change Data Capture in SQL Azure

It has been available in SQL server since 2008, the jump to SQL Azure seems logical.

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.

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

Allowed IP Addresses must be configured in order to connect remotely to Azure Databases (and other services).

While working remotely, instead of having to create a permanent "allowed ip address", allow us to create an allowed ip address for a specific amount of time.

Recently, Microsoft introduced a feature "Global DocumentDB database" along with "multi-homing APIs" which provides transparent & automatic fail-over to secondary database with no human intervention.

It will be helpful to have a similar feature for Azure SQL Database where users can enable Geo-Replication and will not have to worry about manual fail-over to secondary in case when Primary / master is unavailable

I need to work on SQL Server express locally because we are using SQL Azure as our prod environment. The problem is, I am working on my Mac. Is there a way to work around this without using a VM? Can you please make a version of SQL Server to run on Mac OS X?

In the old portal it was possible to view and edit the data of an SQL Server database.
This feature was very compelling to me, and I'd like to see the implementation of it, or at least a temporary reference to it meanwhile.
Otherwise I have to go back and use the old portal.

similar to https://onlinedemo.cerebrata.com/SQLAzureClient/ but integrated into https://windows.azure.com

OData's AtomPub protocol is very verbose. My calculations indicate that AtomPub multiplies Data Transfer Out bytes by a factor of 8.75. (See Querying OData.org’s SQL Azure Northwind Sample Data Service: http://oakleafblog.blogspot.com/2010/03/odataorgs-sql-azure-northwind-sample.html).

Despite the Accept-Encoding: gzip, deflate header, SQL Azure OData responses aren''t compressed. I agree with this comment by Scott Hanselman - failure to compress OData responses is LAME.