Hi, @Richa Nagrath Thanks for posting your question in the Microsoft Q&A forum.
Elastic pools are cost-effective solutions for managing and scaling a group or a pool of Azure SQL Databases, with utilization patterns characterized by low average utilization and infrequent spikes. Whenever the database is hosted in the elastic pool all the resources will be shared among the pool equally for all databases.
Vcores depend on the service tier you will use, vCore model, delivers a much more flexible way of assigning compute resources, Then, measuring the maximum storage bytes utilized by all databases in the pool.
Cost: for ex: if we have 3 databases in the elastic pool with total 100 vCores init.
if the first database is utilizing 10 vcores and the other 2 databases are utilizing 20 vcores each the remaining 70 vcores can be taken by the usage of the 3 databases bases on the utilization.
if the first database requires 10+(or 15vcores) it will take extra 5 vcores from the remaining 70 vcores and utilize them, once the operation done it will release the 5 vcores and again the 70 vcores are free for other databases again. either of the 3 databases can take any number of vcores based on the vcores requirement
You can find more information on Manage multiple databases with elastic pools - Azure SQL Database | Microsoft Learn and Azure SQL databases in logical servers, elastic pools, and managed instances - Microsoft Tech Community
I hope this information helps. please let me know if you have any additional questions.
Regards
Geetha