Richard,

Here is what Microsoft defines as a DTU (but I have also seen on Channel 9 a slightly different explanation - but older 2014 video) -

"The Database Transaction Unit (DTU) is the unit of measure in SQL Database that represents the relative power of databases based on a real-world measure: the database transaction. We took a set of operations that are typical for an online transaction processing (OLTP) request, and then measured how many transactions could be completed per second under fully loaded conditions" - https://azure.microsoft.com/en-us/doc... updated 2/17/2016.

I plan to bump up to the standard level which provides 10 DTUs during my busiest months, but other than the elastic database option (too expensive for me) I am not aware of any dynamic adjustments for the database DTUs.  There is an option to scale out instances of your web app, but that would not help me with the DTUs.

What I really find perplexing is why the 7.4.2 version takes significantly more time to bring up the edit user account dialog than the 5.6.8 version did. Hard to believe that is only due to the Azure DTU limits.

I have been able to determine that using the host account to edit the user account pushes the DTU to 100%, but using just an admin account of the main portal site only pushes it to 60%.  And the other two portals in my installation currently only have admin accounts - no user registration turned on -  and are not even being used right now.

They explain the difference between the basic (5 DTUs) and standard (10 DTUs) levels as:

Basic:  Best suited for a small database, supporting typically one single active operation at a given time. Examples include databases used for development or testing, or small-scale infrequently used applications.

Standard: The go-to option for most cloud applications, supporting multiple concurrent queries. Examples include workgroup or web applications