Skip to main content

Azure SQL DB tiers Short Overview

שלום לכולם
היום אסקור בקצרה את ה tiers השונים לבחירת DB.
במילה tiers מסתתרת משמעות רחבה מאד, טווח רחב מאד של אפשרויות ביצועים.
בפוסט שפרסמתי בחודש מרץ ביצעתי השוואות ביצועים בין tiers שונים:
http://www.sqlazure.co.il/2019/03/azure-sql-db-tiers-comparison.html

והיום אציג טבלה ובה החומרה מתחת לפני השטח נכון להיום!
כידוע יש 2 קבוצות שונות של שרתים שאפשר לבחור עבור Azure SQL DB

  1. DTU
  2. vCore

כאשר באפשרות הראשונה אין אפשרות לבחור קומבינציה של רכיבים - פשוט  בוחרים:
 Basic\Standard1..12\Premium1...15
שזה שוני שנובע מ Local SSD

וכאשר באפשרות השנייה יש אפשרות לבחור בין סוגי CPU שונים
Gen 4 / Gen 5
Gen 4 CPUs are based on Intel E5-2673 v3 (Haswell) 2.4 GHz processors
Gen 5 CPUs are based on Intel E5-2673 v4 (Broadwell) 2.3 GHz processors

שזה גם משפיע על כמות ה RAM
והאם
Busines critical \ General purpose
שגם זה שוני שנובע מ Local SSD
תחת vCore - יש אפשרות לבצע תשלום מראש לכמה שנים ובכך לחסוך המון כסף למי שמשתמש ב  vCore (ועל זה בפעם אחרת)

יש עוד קומבינציות ועוד אפשרויות אבל גם את זה נשמור לפעם אחרת.

מכיוון שאי אפשר לכמת מה יש תחת DTU מבחינת חומרה להלן ההשוואה

 
Tier CPU RAM in GB
s0   1, 1
s1   1, 2
s2   1, 2
s3   2, 9
s4   4, 19
s6   6, 28
s7   12, 56
s9   24, 113
s12  44, 173
p1   2, 9
p2   4, 19
p4   6, 28
p6   12, 56
p11  18, 82
p15  42, 171
GeneralPurpose GP_Gen4_1 1, 4
GeneralPurpose GP_Gen4_24 24, 80
GeneralPurpose GP_Gen5_80 80, 190

 מפה כל אחד ילמד ויבין מה טוב לו
ניתן להסתכל בלינק הבא על כל מיני פרטים נוספים

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-service-tiers-general-purpose-business-critical

את המידע שלפתי לפי השאילתא הבאה:
 
-- CPU assigned to database
SELECT
scheduler_id, cpu_id, status, is_online
FROM sys.dm_os_schedulers
WHERE status = 'VISIBLE ONLINE'
-- Memory allocated to database
SELECT  *, cntr_value / 1024/1024 AS RAM_in_GB
FROM sys.dm_os_performance_counters
WHERE counter_name LIKE '%Target Server Memory%'
 
 
 
Labels:

Comments

Post a Comment

Popular posts from this blog

How to restore deleted Azure Synapse dedicated SQL pool

  Existing dedicated pool can be easily restored from Azure portal or PowerShell command, but for now deleted pool could be restored from PowerShell only! Example: # Connect to Azure with system-assigned managed identity $AzureContext = (Connect-AzAccount -Identity).context # set and store context $AzureContext = Set-AzContext -SubscriptionName $AzureContext.Subscription -DefaultProfile $AzureContext # $AzureContext = Set-AzContext -SubscriptionName $SubscriptionName -DefaultProfile $AzureContext $SubscriptionName="Databases" $ResourceGroupName="stg-rg-we" $ServerName="stg-synapse-we"   $DatabaseName="sql_we_2023_11_07_13_42" $NewDatabaseName="sql_dp_we_deleted" ######################################## $token = (Get-AzAccessToken -ResourceUrl https://database.windows.net).Token $SubscriptionId = "ce088f9e-1111111a3914b" $DedicatedPoolEndPoint = "stg-synapse-we.sql.azuresynapse.net" $DedicatedPoolName = $DatabaseNam...
Post a Comment
Read more

The journey to the Lakehouse

A long time has passed since the last post, we have gone through a long and tedious journey to adapt what Azure offers us, to our needs. Our needs were simple, the Current Datawarehouse (SQL Server on VM inazure) served the BI. ML teams worked on GCP, we want to let both teams to work on Azure in a platform that will have the ability to scale and will not fail every 2 days. We checked: Snowflake on azure Synapse analytics GCP We decided to go for the full Azure product for the reasons: Migration time support costs Synapse as a platform contains many components, and the challenge was to find what fits  us as an organization and as a group. The knowledge of the people and their abilities influenced the plans. Here's what we planned and what we did: We start to put everything in the Data Lake in parquet or delta format, build on top of Azure ADLS gen 2. We had to move some data to T-SQL compatible platform, so this involves setting up a dedicated Synapse pool , which is a fully man...
Post a Comment
Read more

From DBA to Data Engineer in Azure

I recently moved a role From being a DBA Manager, Who is responsible for the operational databases. I moved to manage the data engineering group. So what exactly is the difference between the two functions? DBA - Production Databases: SQL\ NoSQL- 24*7, powerful server on premise or on the cloud, managed or semi managed, security tasks, high performance is a target, multiregional, HA as top priority. Developers are using Microservices - so we have many applications many services and many many Databases. Many kinds of DB's like Cloud IAAS and PAAS. Secure and audit the data is must. The Clusters must have Uptime as long as we can achive. Data Modeling - is so important too. Challenges and Problems in the data bases systems Lots of DB’s Lots of creators / no standards Lots of Consumers (Query, tools, SLA) Raw data Lots of data resources Data silos In Data Engineering we have other challenges for example we have Data lake and Data Warehouses : Batch process. Stream Process. many data ...
Post a Comment
Read more