Azure SQL Database Resource Limits,

Azure SQL Database Resource Limits. Azure SQL as an service database limitation

SQL Database is a general-purpose relational database service in Microsoft Azure that supports structures such as relational data, JSON, spatial, and XML. It delivers dynamically scalable performance.

SQL Database shares its code base with the Microsoft SQL Server database engine. With Microsoft’s cloud-first strategy, the newest capabilities of SQL Server are released first to SQL Database, and then to SQL Server itself. This approach provides you with the newest SQL Server capabilities with no overhead for patching or upgrading – and with these new features tested across millions of databases. For information about new capabilities as they are announced, see:

Azure SQL database Limitation /benefits /highlights :-

1> you can create new database from sample database of from backup of another database or new blank database

2> there are 2 options to create new database one is with elastic pool and another without elastic pool

3>we can create up to 5000 database per sql backend server

4> Every database come with point in time backup with specific restore point (based on sql plan). data retention period for basic  is 7 days, 14 days for standard , 35 days for premium. apart from point in time we can also configure additional backup for SQL database using azure recovery vault (additional cost involve)

5> Every azure sql database can be copy to another backend server but we can not change plan while coping database

6> Azure sql database allow to change DTU (data transaction unit) / plan at any time  but cant change database from non elastic to elastic pool.

7> You can have up to a max of 45000 DTUs per server

8> you can access SQL by using public url and credentials provided while creating sql or you can also add azure AD authentication to server level and then use Azure AD token base auth.

note – Within this model point-in-time restore is designed for recovering a database from a recent backup after accidental data corruption or deletion.

BCDR option

Basic tier

Standard tier

Premium tier

Point In Time Restore Any restore point within 7 days Any restore point within 14 days Any restore point within 35 days
Geo-Restore ERT* < 12h RPO† < 1h ERT* < 12h RPO† < 1h ERT* < 12h RPO† < 1h
Standard Geo-Replication Not included ERT* < 30s RPO† < 5s ERT* < 30s RPO† < 5s
Active Geo-Replication Not included Not included ERT* < 30s RPO† < 5s

* Estimated Recovery Time (ERT) – The estimated duration for the database to be fully functional after a restore/failover request. † Recovery Point Objective (RPO) – The amount of most recent data changes (time interval) the application could lose after recovery.

 

 

(Visited 2,743 times, 1 visits today)
One Comment

Add a Comment

Facebook