While designing or during the meetings this is a very common question that customer asked. What is good for us regarding SQL as there are multiple options available in the Azure for SQL. Well the answer is obvious what yon want the most as per below points -
- Cost
DBaaS or PaaS is always cheaper then IAAS as administration of underlying OS and hardware is not yours. DB automatically configured , Patched and upgraded by MS which reduces Administrative cost in addition to this in-built capability of back-ups.
- Administration
PaaS SQL you only need to worry about Database but in IAAS you have full control over OS and Sql server instance configuration & you can decide when to update or upgrade and other admin tasks.
- SLA
Both IaaS and PaaS provide high, industry standard SLA. PaaS option guarantees 99.99% SLA, while IaaS guarantees 99.95% SLA for infrastructure, meaning that you need to implement additional mechanisms to ensure availability of your databases
- Time to move to the Azure
Both IAAS and managed instances are very easy to migrate just like on-prem from one server to another , may require little changes in managed. If we are moving to Paas / elastic pools we need tp be sure because certain features not supported e.g authentication and few other features.
- Size of DB
Size of DB also matters because managed instance dont support more then 8TB and Iaas VM 64 TB.
Lets discuss all the available option we have on azure :-
1 - Azure PaaS Sql Db ( elastic pool feature is there)
2 - Managed Instance
3 - SQL on Azure VM
Lets see the main difference between these 3 first and then will see what is best for you :
Post is getting little bigger hence , will be talking about the best use scenario in next post. After reading you would have pretty good idea who does what and where you can save money what serves all the features and where you can have administrator tasks etc etc. This would help you for sure to figure about what SQL service you need to opt for however you can easily do the assessment by DMA to be sure if you DB is good to migrate to Azure SQL if that is your choice.
Below is the reference link :
- Cost
DBaaS or PaaS is always cheaper then IAAS as administration of underlying OS and hardware is not yours. DB automatically configured , Patched and upgraded by MS which reduces Administrative cost in addition to this in-built capability of back-ups.
- Administration
PaaS SQL you only need to worry about Database but in IAAS you have full control over OS and Sql server instance configuration & you can decide when to update or upgrade and other admin tasks.
- SLA
Both IaaS and PaaS provide high, industry standard SLA. PaaS option guarantees 99.99% SLA, while IaaS guarantees 99.95% SLA for infrastructure, meaning that you need to implement additional mechanisms to ensure availability of your databases
- Time to move to the Azure
Both IAAS and managed instances are very easy to migrate just like on-prem from one server to another , may require little changes in managed. If we are moving to Paas / elastic pools we need tp be sure because certain features not supported e.g authentication and few other features.
- Size of DB
Size of DB also matters because managed instance dont support more then 8TB and Iaas VM 64 TB.
Lets discuss all the available option we have on azure :-
1 - Azure PaaS Sql Db ( elastic pool feature is there)
2 - Managed Instance
3 - SQL on Azure VM
Lets see the main difference between these 3 first and then will see what is best for you :
| SQL Server on VM | Managed instance in SQL Database | Single database / elastic pool in SQL Database |
| You have full control over the SQL Server engine. | High compatibility with SQL Server on-premises. | The most commonly used SQL Server features are available. |
| Up to 99.95% availability. | 99.99% availability guaranteed. | 99.99% availability guaranteed. |
| Full parity with the matching version of on-premises SQL Server. Fixed, well-known database engine version. | Latest stable Database Engine version. | Latest stable Database Engine version. |
| Easy migration from SQL Server on-premises. | Easy migration from SQL Server. | Migration from SQL Server might
be hard. Some SQL Server features are not available. |
| Private IP address within Azure VNet. | Private IP address within Azure VNet. | Private IP address cannot be assigned (you can limit the access using firewall rules). |
| You have ability to deploy application or services on the host where SQL Server is placed. | Built-in advanced intelligence and security. Online changes of resources ( CPU/Storage) | Built-in advanced intelligence and security. Online changes of resources ( CPU/Storage) |
| You need to manage your backups and patches. | No need to manage patches and inbuilt backup is there | No need to manage patches and inbuilt backup is there |
| You need to implement your own High-Availability solution. | Built-in HA that is deeply integrated with Azure platform. It is dependent on service fabric for failure and recovery in addition to that azure sql leverages AOAG | Built-in HA that is deeply integrated with Azure platform. It is dependent on service fabric for failure and recovery in addition to that azure sql leverages AOAG |
| There is a downtime while changing the resources(CPU/storage) | Online change of resources (CPU/storage). | Online change of resources (CPU/storage). |
Post is getting little bigger hence , will be talking about the best use scenario in next post. After reading you would have pretty good idea who does what and where you can save money what serves all the features and where you can have administrator tasks etc etc. This would help you for sure to figure about what SQL service you need to opt for however you can easily do the assessment by DMA to be sure if you DB is good to migrate to Azure SQL if that is your choice.
Below is the reference link :
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-paas-vs-sql-server-iaas
https://pachehra.blogspot.com/2019/07/what-sql-is-good-for-you-azure-part-2.html
https://pachehra.blogspot.com/2019/07/what-sql-is-good-for-you-azure-part-2.html
No comments:
Post a Comment