Re-order steps in creating a new SQL Database
Taking an Azure class now - When creating a new SQL Database, the lab instructions state to specifically set "Subscription" FIRST then "Resource Group", etc. If the order of steps are important to be done sequentially, can you just place the items in the order of importance in the UI (rather than the user going to the bottom then back to the top)?
Gerald Wiltse commented
I am amazed at how frustrating and unforgiving the new portal is when creating resources. Here is one specific element that can be fairly easily improved. This has been a problem for over a year, I assumed it would get fixed quickly. It didn't.
Here's what's happened multiple times.
In a hurry, browse SQL Databases, filter by my desired subscription "IT Subscription". Database I want doesn't exist yet, need to create:
Click Add Database
Define a Name
Select "new database server" -> Define all the associated options for that
Select Pricing Tier
Select Collation Options
Select Resource Group... wait... these aren't the right resource groups.
Select correct subscription.... oh god, everything lost, start from scratch
This is a very basic UX Flaw. Because resource group and database server are dependent children of the subscription selection, they should not appear as neighbors to it in the selection list, and CERTAINLY should not appear BEFORE it...
Please at LEAST make Subscription the FIRST choice on the list, since it determines the options that follow. A more appropriate fix would be to represent them as parent/children. In the case of the new UI, I suppose this would spawn more blades which is pretty gross IMO. Still it might be the right solution.
However, a more broadly useful improvement for this situation would be to permit the migration of things from subscription to subscription, and RG to RG after built.
I know, there are other requests for this already, and i'm sure it's extremely difficult on the backend (otherwise it would be done). This is one of those reasons why it is so.
I have two subscriptions. I started the UX for creating a new DB and filled down the information in a top-down fashion (specifying the server parameters to start) before realizing that the subscription needed to be changed (at the bottom of the screen). Once I changed this, it invalidated several of my previously made choices (e.g. server and resource group).
Dan Ciborowski commented
Changing Subscription (step 6), should not restart step 1
Tomas Ekenman commented
When creating a new sql database, the option for subscription is the last one. Since all other choices depends on this one it should be placed first. It took me a while to find out why my current databases didn't show.