In today’s article we will examine Azure SQL Database and Architecture.<\/p>\n
Azure SQL Database is a highly scalable and multi-leasable highly available Platformas-a-Service (PaaS) or Database-as-a-Service (DBaaS) database service from Microsoft.<\/p>\n
Microsoft; operating system, disk management, network, virtualization, version transitions, server installation and maintenance work for us. We only use the database.<\/p>\n
Azure SQL Database has the following deployment options.<\/p>\n
single<\/p>\n
Elastic Pool<\/p>\n
Managed Instance<\/p>\n
Azure SQL Database allows its users to focus solely on managing data and works on four layers to provide users with relational database functionality.<\/p>\n
Client Layer<\/p>\n
Service Layer<\/p>\n
Platform Layer<\/p>\n
Infrastructure Layer<\/p>\n
Client Layer<\/h4>\n
The Client Layer acts as the interface for applications to access a SQL database. It can be in an On-Prem environment or on Azure.<\/p>\n
SQL Server communicates with applications using Tabular Data Stream (TDS \u2013 application layer protocol created to transfer data between a database server and a client).<\/p>\n
These applications can be .NET, ODBC, ADO.NET. It can be connected to Azure SQL Database without any additional requirements or installation in Java.<\/p>\n
Service Layer<\/h4>\n
The service layer acts as a gateway between the client and platform layers and is responsible for the following operations.<\/p>\n
Creating the SQL Database.<\/p>\n
Controlling Access to SQL Database<\/p>\n
Providing SQL Firewall service and enforcing security<\/p>\n
Generating invoice for SQL database based on usage amount<\/p>\n
Routing connections between the client and Azure SQL<\/p>\n
Platform Layer<\/h4>\n
The platform tier consists of physical servers hosting SQL databases in data centers.<\/p>\n
Each SQL database is stored on a single physical server and multiplexed on two different physical servers for high availability.<\/p>\n
Together with the created database server, it creates three different physical servers (You can see in Picture1. The platform layer has two components.<\/p>\n
Azure Fabric: Responsible for load management and controls automatic failover of SQL databases between servers.<\/p>\n
Management Services: It deals with the health status of a single server, patch updates.<\/p>\n
Infrastructure Layer<\/h4>\n
The infrastructure layer is responsible for managing the physical hardware and operating system.<\/p>\npicture1<\/figcaption><\/figure>\n
The application sends a TDS \u2013 Tabular Data Stream \u2013 request to the SQL Database (Login, DDL, DML operations etc.) TDS validates the request at the service layer to the network layer before sending the request to the platform layer and then forwards it to the platform layer.<\/p>\n
If the incoming request was forwarded directly to the platform layer by TDS, login and firewall controls would not have been achieved, and perhaps you would have been subject to a dDos attack.<\/p>\n
As shown in Picture2, the Platform layer has three nodes. Each node has a primary copy of an sql database and a secondary copy of two different physical servers, two different sql databases.<\/p>\n
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2020\/12\/Resim-1.jpg\")
![\"\"](\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/08\/img_630e325637df2.png\")