Skip to main content

Monitoring AWS RDS for SQL Server VS Monitoring SQL Azure

Hi
I want to show you now the GUI ways to monitor the Main SQL Servers on the Azure and on AWS RDS. 
I said GUI since I will not show here the queries in both platforms, T-SQL Queries that show us all we need.
I will just show the GUI aspects.

Lets jump into it AWS RDS Monitoring:

In the AWS Main Portal we have list of DB's we have in AWS we have (this is the new look of the portal):

When I will click on Show Monitoring we will see lots of charts related to the status of the Instance.
when I move to each instance I can see the relevant charts to this instance. 


We can see here some Metrics like CPU, IOPS, free space i left in the instance or Throughput, those are very useful parameters. We can see those metrics in several time resolution.
And you can create Alarm if one reach the red line you want.



And the screen to create alarm looks like this:


So the main Monitor From the Portal is very good and by several clicks you can monitor all instances.

Another way to Monitor is Via SSMS. we have the great tool called the 'Activity Monitor'.
in that tool you can see almost all you can see in regular on-premise servers, you just need to be connected to AWS RDS for SQL Server:



so here the monitor is opened and you can see some metrics as regular SQL Server, only the CPU monitor is disable




--------------------------------------------------------------------------------------------

Now lets start with Windows Azure SQL DataBase:
Lets start with the end, we do not have  'Activity Monitor' on SQL Azure - since the SSMS knows it is a separate version, so we can not open it.




Second Issue: Monitor from the Portal, we have basic screen show us connections and deadlock , if we want more details like free space we can go into the DB itself in the portal and see free space ect..



The Last part in third party applications i will show one example - it is QUEST Software - Foglight for SQL Server, it come free if you have it for on-premises DB's.
it really gives you a lot of data - also you can change configurations or pricing... Greate tool!!! - we do not have it yet on AWS RDS for SQL Server...









Summery:
If we will test each platform by itself AWSRDS has more tools and interfaces to monitor the DB activities.
If we will add tools from third party SQLAzure has a lot what to sale.

Lots of DBA's do not love to Monitor DB's via GUI, they prefer queries, and this is a wrong way of thinking. DB's  in the Cloud need tools.

so this is a short summery - I will continue tests the 2 good platforms.
have a nice day
pini

Labels:

Comments

Post a Comment

Popular posts from this blog

Extended Events in SQL Azure

Hi Everybody   Today an English post about 'Extended Events in SQL Azure', some of you shorten the name to 'EE' and some to 'XEvent'. I Love EE so this is how I will call it in this post.   This feature was introduce in SQL Server 2008 and its should help collecting DATA about what is running in the Server.   More Details about this SQL Server feature can be found in this Link: https://msdn.microsoft.com/library/bb630282.aspx?f=255&MSPPError=-2147217396   There are a few differences between EE in SQL Azure and regular SQL Server: In SQL Server versions the EE are on the Server level and therefore you create sessions on Server. In SQL Azure the server is a virtual entity - so the EE is in DB level and you create the session on DataBase. In SQL Server versions the EE can write to files on the server. SQL Azure does not have drives for files (SQL Azure is PAAS.....:-)). There is an option to write to blob storage, for this we need t...
Post a Comment
Read more

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