Hi,
You can check the pricing model here. Overall you are charged based on the number of vCores used per second and also for the provisioned storage per GB. In case you have auto-paused enabled once the database is paused your are not charged for the vCores but you are charged for the storage provisioned. Note that auto-pause is triggered when:
- Number of sessions = 0
- CPU = 0 for user workload running in the user resource pool
So the prices does not increase if you make more SQL calls but if you have auto-paused configured and you make calls that will start the database the cost will increase. So in case you want to save on cost do not make SQL calls that are not necessary when the database is paused. As I have already mentioned you are charged for the provisioned database size not for the used and that charge is happening no matter if the database is paused or not. I would advise you when possible to update the table rather delete it and re-create it. The latter will most likely take more time to execute thus increases your usage of the database and decreases the time when the database can be paused (if pause configured). I do not know what do you mean by refreshing but every time you try to use the database (connect to it) and it was paused it will wake the database and additional cost will occur. Overall you have constant charge of the storage and charge about the vCores used based on the usage of the database if auto-paused is configured. In general if you have database that is used a lot I would configure the auto-pause to be not so aggressive. If you have database that is not used so much you can configure more aggressive auto-pause.
Serverless compute tier for Azure SQL Database
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.