Skip to main content

Cross Database Queries in SQL Azure DB - Part 2

Hi All
 
So After a month of using Cross Database Queries in SQL Azure DB, I can say that we have a very useful tool.
 
We can use in many scenarios, I will show today one.
 
We are using 10 shards DB's to balance read operations to many DB's. The write operations goes to the DB's as well.
 
I' as a DBA wants to know the status of all DB's, so instead of creating PowerShell that connect to all of the DB's I have created external tables in 1 DB that reads the  
 
sys.dm_db_resource_stats 
 
from all DB's' so I have now 1 real table and 9 external tables.
 
I have created a view that reads from al 10 tables' and now I see all data from all shards.
 
I also put it in PowerBI and I see it in a visual way - and also in my Mobile.
 
Here I have in the first line DTU AVG value for each shard in the last 10 minutes, 1 clock that avg all shards.
 
The second line is the DTU real value in the last 10 Minutes per Shard.
The Third line is the DATA IO value in the last 10 Minutes per Shard.
 
 
 
I More thing, in ssms in sql server 2016 you have special place for external tables:
 
 
 
 
But in SQL Azure - not yet, and even if you will run create script you will not see it.... just use :
 
select * from sys.external_data_sources
select * from sys.external_tables
 
enjoy.
 

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

Back to Basic - create new Azure SQL DB

Hi All Long time no posts, i have been busy in last few months on a hard day 2 day work and did not  had the chance to publish some posts. So i have decided to sit and write some "Back to Basic" posts. Today i will write about how to create an Azure SQL Db from the portal. Choose the Subscription. RG - if its in special Project connect to its RG (Resource group is a virtual collection of resources in order to easy manage budgets.) DB Name Server - choose the correct or create one(Server has limited manage capabilities on the DB like security, backup policies and other rules) Choose no (elastic pool is a feature that will not be explained here) This is the server tier, means the power of the DB and by pass the payments of the DB (i will have special post on the new tiers options, for this post i will leave the default) This is the Storage redundancy , for now leave it in the default option. now we will move to the Networking tab: 8 - 9. Configuration of networking and s...

Configuring secondary database in Azure SQL DB - Bug found

Hi All Last week we had an issue with a secondary DB in geo replication and fail over group. To make the long story short we had to delete the secondary and recreate a secondary from scratch . And now let me tell you the story, we build a DB in P6 tier - very high, expensive and highly available. Then we add a geo replication copy via the platform, like it shows here. This is take from MSFT documentation: https://docs.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview It is written:  " Both primary and secondary databases are required to have the same service tier. It is also strongly recommended that the secondary database is created with the same backup storage redundancy and compute size (DTUs or vCores) as the primary. If the primary database is experiencing a heavy write workload, a secondary with lower compute size may not be able to keep up with it. That will cause redo lag on the secondary, and potential unavailability of the secondary. To mit...