In the Azure portal (old as well as new), the list of databases is empty, where it should show one. In the old portal, there is a warning message saying:

The databases for server <deleted> located in region West Europe for subscription <deleted> could not be retrieved. Please wait a few minutes and then try this operation again. For more information about Microsoft Azure service availability, visit the Microsoft Azure Service Dashboard.

(The <deleted> show the actual db name and subscription)

This message has been there for a few hours. The database itself is still up and running, I can connect to it without any issues. The dbserver page on the portal does not give any indication of problems, and the Azure Service Dashboard is green all over the board.

My biggest problem is that I scaled the DB up to P3 this morning, because I needed to do some heavy lifting, but now I can't scale it back down to S3.

How do I fix this?

Any ideas (or pointers to ideas) are welcome!

Thanks,

Tim

Tim,

    As you are able to connect to the database, you can use T-SQL statement 'Alter Database ... Modify..' command (https://msdn.microsoft.com/en-us/library/ms174269.aspx) to scale the database up/down. As for the original issue, can you please send the logical server name and we can take a look.

thanks

Thank you for your reply. The logical server name is dbfpdm01.

I have tried to use the Powershell commands to downgrade, using the commands shown HERE

(using S2 as serviceobjective, because S3 was not available apparently, and using the -Edition Standard, instead of Premium)

But I'm not sure if this worked. The command

Get-AzureSqlDatabase -ServerName "dbfpdm01" -DatabaseName "dbfpdm01"

does not return. (read: it hangs my powershell session)

Regards,

Tim

I have the same issue - I'm getting a warning message in both portals saying the databases could not be retrieved (US East). I can access the databases in SSMS, and websites can access the db as well.

    This issue is being actively investigated by Microsoft currently and will be resolved as soon as possible.

thanks

Srini

• Proposed as answer by Guy Haycock [MSFT]Microsoft employee, Owner Friday, January 30, 2015 1:09 AM

    This issue is being actively investigated by Microsoft currently and will be resolved as soon as possible.

thanks

Srini

• Proposed as answer by Guy Haycock [MSFT]Microsoft employee, Owner Friday, January 30, 2015 1:09 AM