Azure SQL Database Options
- Database Options
Azure SQL Server Options
- Server Options
Azure SQL Database Failover Groups
- Need for Database Failover Groups (We already have Geo-Replication)
- Geo-Replication is easy to configure. but it has some drawbacks
- Support for simultaneous replication and failover of multiple databases.
- There is need for manual failover in Geo-replication.
- Geo-Replications use asynchronous replication which might lead to data loss
- The above problems are addressed in Auto-failover groups
- Navigate to the SQL Server Created and Click on Failover Groups Blade and add a new fail over group and configure the failover groups server name
- In the case of primary server outage then failover is automatic, Azure also gives options for manual failover and forced-failover
Azure MySQL, MariaDB , Postgres
- These are managed db engines in Azure
- This is premium offering of NOSQL from Azure
- It is globally distributed and multi model no sql service, that can scale and replicate data to any number of azure regions
- Always on: SLA for high Availability is 99.99%
- Elastic scalability to read and write is offered b Cosmos DB. With Single API call yu can scale upto thousands to hundreds of millions of requests per second across globe.
- Secure by default.
- Cosmos DB Supports APIs for storing and interacting with Data
- SQL API
- MongoDB API
- Gremlin API
- Table API
- Cassandra API
- Etcd API
- Create a Cosmos db Refer here