Number of concurrent transactions supported for an Azure SQL 4 vCores

Hi, there is not a single fixed "number of concurrent transactions" for an Azure SQL database based only on 4 vCores.

Concurrency depends heavily on what each transaction does. A 4-vCore database can handle many small, short transactions, but only a few heavy transactions if they are doing large scans, waiting on locks, writing heavily to the log, or consuming tempdb/CPU.

For sizing, I would load test with your real transaction pattern and watch CPU, data IO, log IO, waits, blocking, sessions, and worker usage. Since this is General Purpose serverless, also pay attention to min vCores, auto-pause, and cold-start behavior. The vCore count tells you the compute envelope, but the workload shape decides the practical concurrency.