Skip to main content

New Metric for SQL Azure - DTU

שלום לכולם
וכן גם זה סוף סוף הגיע, מה הגיע? מידע - שהיה חסר לנו.
אז מה היה חסר לנו?
כאשר יצרו ב SQL Azure את 3 השכבות - ההבדלים ביניהם הוגדרו לפי מושג שנקרא DTU - שהיווה שיכלול של טרנזקציות לשניה ועוד מספר מדדים:

Service Tier Performance Level DTU
Basic   5
Standard S1 20
Standard S2 50
Premium P1 100
Premium P2 200
Premium P3 800


אגב עוד נושא חדש שיהיה החודש זה tier חדש - S0, אבל זה נושא אחר.

בקיצור ה DTU שצרכנו לא היה ידוע ולאחרונה הוסיפו אותו למוניטור בפורטל.
הנה תמונה של שני בסיסי נתונים באחד הצריכה היא כמעט כל הזמן 100% - מה שאומר שאולי לא תהיה לי ברירה אלא לשנות קוד או לשדרג לשכבה יותר יקרה.
הוסיפו מטריקה זו ל monitor שלכם ותהנו.
אגב טרם מצאתי את ה View שמכיל מידע זה.



Comments

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...

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...

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 ...