About Azure SQL Database

Jonas 

So, there's two states which mean different things for the compute resources (CPU and memory):

1. The SQL "serverless" service is running;
2. The SQL "serverless" service is stopped (which is called "auto-paused").

The SQL service is running

• This is like when a computer is switched on, meaning you are paying for using CPU, memory and storage;
• If the SQL workload is light, the amount of memory and CPU will likely be towards the lower value limits you entered on the configuration page, which translates into a lower bill when it comes time to pay (since you only pay based on utilisation);
• If the workload is busy, the amount of memory and CPU will likely be towards the upper limits you entered on the configuration page;
• If there's no SQL workload at all for the timeframe specified as the "duration" on the configuration page, then the SQL "serverless" service is stopped (called "auto-paused").

The SQL service is stopped (auto-paused)

• This is like when you shut down a computer;
• CPU and memory are no longer being used as the SQL instance is effectively "switched off";
• This means you are saving money, as Microsoft isn't billing you for CPU or memory as the SQL instance is "switched off";
• You are still charged for storage while the instance is switched off;
• You don't have to "turn the SQL instance back on" again, as that will happen automatically once any kind of workload tries using the SQL instance again (although there will be a delay and things will run a bit slower for a short while after it starts itself back up again).

Cheers,

Lain