Skip to main content

SQL Azure Geo Replication

Hi
Today i will publish a post of a friend, Yitzchak Wahanon - @YitzWahanon

He wrote this post about Premium Tier, but meanwhile we have non readable replica in Standard Tier too.
Its all of the same but the main change is - that its not readable. Only MSFT will decide if it will be available for us.

This Post include lots of images, its important to understand the Process.

Creation

Already have 1 Server, so need to start by creating the database.
Create a new database
Needs to be Premium Edition:



 Create a new server in a different Geo location.

Within the Source database, Click on Geo_Replication: - Click on “Add Replica” at the bottom


Choose Server - obviously in a different location to the source:




 Accept to pay lots of money:



Progress and steps are reported at the bottom of the screen:


 If you connect to the secondary server then you can see that the database is being copied


 Go back to the source and it will show that the geo-replication is active



Now configure IP access to the new server.


Testing

Insert a record in the Source and see it almost immediately replicated to the Copy


 Try Inserting into the Copy



 Create another server in another geo location and another replica



In the SQL Databases you now have 


 Try changing the scale of a replica


 Try changing the scale of the master:


Stop the replica on the master































































Note the Geo-Replication screen takes time to update.

After you stop geo-replication the Copy database still exists, just marked with “None” in the Replication column. The database is also read/write now





















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