A DTU is a unit of measure for the execution of an administration level and is a synopsis of a few database qualities. Every administration level has a specific number of DTUs relegated to it as a simple approach to analyze the execution level of one level versus another.

Database Throughput Unit (DTU): DTUs give an approach to portray the relative limit of an execution level of Basic, Standard, and Premium databases. DTUs depend on a mixed measure of CPU, memory, peruses, and composes. As DTUs build, the force offered by the execution level increments. For instance, an execution level with 5 DTUs has five times more power than an execution level with 1 DTU. A most extreme DTU amount applies to every server.

The DTU Quota applies to the server, not the individual databases and every server has a most extreme of 1600 DTUs. The DTU% is the rate of units your specific database is utilizing and it appears that this number can go more than 100% of the DTU rating of the administration level (I accept to the furthest reaches of the server). This rate number is intended to help you pick the fitting administration level.

For instance, if your DTU utilization demonstrates an estimation of 80%, it shows it is devouring DTU at the rate of 80% of the breaking point a S2 database would have. On the off chance that you see values more prominent than 100% in this perspective it implies that you require an execution level bigger than S2.

As an illustration, suppose you see a rate estimation of 300%. This lets you know that you are utilizing three times a larger number of assets than would be accessible in a S2. To decide a sensible beginning size, think about the DTUs accessible in a S2 (50 DTUs) with the following higher sizes (P1 = 100 DTUs, or 200% of S2, P2 = 200 DTUs or 400% of S2). Since you are at 300% of S2 you would need to begin with a P2 and re-test.