SQL Databases -> New -> Data Services -> SQL Database -> Custom Create
- Name: SomeDatabase
- Subscription: {my subscription}
- Service Tier: Standard
- Performance Level: S3 (100 DTUs)
- Max Size, Collation: defaults
- Server: All current servers are shown in the list but the only active selection is "New SQL database server" so I select that.
When creating new SQL database server I supply new credentials for the admin account, select my region and check "Allow Windows Azure Services to access the server." then I click the check mark button to finish.
In the notifications area of my Azure Portal session I receive the following:
Could not submit the request to create database 'SomeDatabase'.
- Successfully created server '{server name}'.
- Could not submit the request to create database 'SomeDatabase'. The edition 'Standard' does not support the service objective '789681b8-ca10-4eb0-bdf2-e0b050601b40'.
Afterwards the new database is not listed under my SQL Databases area however, any new database I create has the server I just created available for use. If I select that new server the S3 level is not available and if I select S3 during new database creation I'm back to only being able to select a new server creation.
- Edited by Dane Vinson Friday, December 19, 2014 8:43 AM