You are evaluating whether an Azure SQL Database elastic database pool suits your workload and usage patterns. What are two possible ways to identify the elastic database transaction units (eDTUs)? Ea

`sys.dm_os_wait_stats` helps identify performance bottlenecks by showing what resources SQL Server threads are waiting on, but it does not directly quantify eDTU usage or overall resource consumption. Its purpose is for bottleneck analysis, not eDTU identification.

The Database Engine Tuning Advisor recommends database design changes like indexes and statistics to improve query performance, rather than analyzing or reporting on eDTU usage or resource consumption. Its focus is on schema optimization, not service tier sizing.

The Service Tier Advisor is not a recognized or standard tool or dynamic management view (DMV) within Azure SQL Database specifically for identifying eDTU usage patterns. There is no official Azure SQL Database feature by this name that performs this function.

`sys.dm_db_resource_stats` provides detailed resource usage statistics for an Azure SQL Database, including DTU and eDTU utilization percentages, which are crucial for understanding current and historical resource consumption patterns. Aggregating this data directly helps in determining the appropriate eDTU level for a workload.

`sys.dm_os_performance_counters` exposes various performance counter information from the SQL Server instance, such as CPU, I/O, and memory usage, which are fundamental components of eDTU consumption. Analyzing these counters can indirectly infer the resource demands that contribute to the overall eDTU requirement of a database or elastic pool.