![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 83%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Azure SQL Database
An Azure relational database service.
6,186 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 49%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVK%3C/text%3E%3C/svg%3E)
Hi @Aditya Singh,
Greetings!
We would like to inform you that, to support the growth of your SaaS app from 10,000 to 100,000 users, ensuring scalability, performance, and cost efficiency, the vCore-based pricing model for Azure SQL Database is recommended.
Regarding the Azure SQL Database Pricing Plan:
vCore -based vs. DTU -based Pricing Plan
vCore-based Model:
- Flexibility and Control: Allows you to independently choose and scale compute and storage resources based on your workload needs.
- Service Tiers: Offers three service tiers: General Purpose, Business Critical, and Hyperscale, providing options to match your performance and cost requirements.
- Cost Efficiency: Enables you to use Azure Hybrid Benefit for SQL Server to save costs.
DTU-based Model:
- Bundled Resources: Provides a bundled measure of compute, storage, and I/O resources, which might be simpler but less flexible.
- Preconfigured Options: Suitable for customers who prefer simple, preconfigured resource options.
For more information, please click on the following link https://learn.microsoft.com/en-us/azure/azure-sql/database/purchasing-models?view=azuresql
Regarding the Speed and bandwidth considerations for handling large volumes of data and users:
- Scalability and Performance: Ensure your system can scale effectively to accommodate growing data volumes and user demands. This involves choosing a database or processing framework that can expand as needed, whether through horizontal scaling (adding more servers) or vertical scaling (upgrading existing hardware).
- Performance Optimization: Implement techniques such as indexing and caching to maintain fast response times even as the workload increases. For more information, please click on the following link https://airbyte.com/data-engineering-resources/best-practices-deployments-with-data-volumes
Regarding the cost and best practices for charging based on usage in an SaaS model:
There are several SaaS pricing models you can consider:
- Flat-rate Pricing: Charges a single, fixed price for all users, regardless of usage.
- Usage-based Pricing: Charges based on the actual usage of the service, which can be more cost-effective for users with varying usage patterns.
- Tiered Pricing: Offers different pricing tiers based on the features or usage levels.
- Per-user Pricing: Charges based on the number of users accessing the service.
- Freemium Pricing: Provides a basic version for free and charges for premium features. For more information, please click on the following link https://www.marketermilk.com/blog/saas-pricing-models
Regarding the Support for multiple databases and interlinking databases within the system.
Azure SQL Database offers several features to support multiple databases and interlinking:
- Elastic Pools: Allows you to share compute resources between many databases on the same server, providing performance elasticity and cost efficiency.
- Elastic Database Tools: Supports sharding, enabling you to scale your workload across multiple databases.
- Elastic Query: Enables you to run Transact-SQL queries that span multiple databases, allowing cross-database queries and integration with tools like Power BI. For more information, please click on the following link https://learn.microsoft.com/en-us/azure/architecture/guide/multitenant/service/sql-database and https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overview?view=azuresql
Regarding the Upgrading and Degrading Database Performance:
Azure SQL Database allows you to dynamically scale resources with minimal downtime:
- Scaling Resources: You can easily change resources (CPU power, memory, IO throughput, and storage) allocated to your databases via the Azure portal using a slider.
- Service Tiers: You can change the service tier, compute tier, and resource limits for a database, elastic pool, or managed instance at any time. For more information, please refer to this parallel thread https://stackoverflow.com/questions/64008190/how-can-i-join-tables-from-different-databases-in-azure-sql-saas and https://learn.microsoft.com/en-us/azure/azure-sql/database/scale-resources?view=azuresql
Regarding the Data Retrieval Options in Case of Data Deletion:
Azure SQL Database provides several options for data recovery:
- Point-in-time Restore: Allows you to create a new database on the same server, recovered to a specified point in time within the retention period.
- Deletion Time Restore: Enables you to create a database on the same server, recovered to the deletion time for a deleted database.
- Long-term Retention Restore: Allows you to create a new database on any server in the same region, recovered to the time of a recent backup.
- Geo-restore: Enables you to create a new database on any server in any other region, recovered to the point of the most recent replicated backups. For more information, please click on the following link https://learn.microsoft.com/en-us/azure/azure-sql/database/recovery-using-backups?view=azuresql&tabs=azure-portal
I hope this information helps. Please do let us know if you have any further queries.
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.