Skip to main content

SQLAzure and Amazon RDS for Microsoft SQL Server

The Air battles just began, it will be great fight and the clients will be the main beneficiaries.

Amazon just release (after they for few years Oracle and MySql DB’s) Support for Microsoft SQLServer, you can put on AWS SQLServer 2008R2. by using your License or use their with full package.

You do not need to install – the AWS will do it.

I will write long Post in Hebrew – and you can translate it, I will write goods and beds of each SQL service.

Now those 2 huge, technology companies are fighting in the same Battlefield, but Amazon put MSFT in a very deep conflict, they want everyone uses SQLServer, but from Amazon RDS too? sure they want…  but then what about SQLAzure??? very deep and complicated dilemma…

קרבות האוויר רק החלו, זה יהיה קרב גדול ונראה כי הלקוחות יהיו הנהנים העיקריים.
אמזון שיחררו (לאחר שנים אחדות שכבר היה אצלם אורקל ו-MySQL ) תמיכה ל SQLServer כל אחד יכול בלחיצת כפתור להפעיל  2008R2 SQLServer. באמצעות רשיון או להשתמש בשלהם עם החבילה המלאה.
אין צורך להתקין - AWS יעשה את זה.
אני אכתוב פוסט ארוך בעברית - אני אכתוב על יתרונות וחסרונות  של כל שירות SQL. כמו למשל מה יש ב RDS ואין ב Azure, לדוגמא גיבויים או רפליקציות, ומצד שני אתה עובד בגירסת 2008 וכשתירצה לשדרג זה ייקח משאבים.
שתי חברות טכנולוגיה גדולות אלו נלחמות בשדה הקרב האכזרי של הענן, אמזון שמה את  MSFT בקונפליקט עמוק מאוד, מצד אחד MSFT רוצים שכולם ישתמשו ב SQLServer, אבל מצד שני לא באמזון RDS אלא ב AZURE. זוהי דילמה מאוד עמוקה ומורכבת ל MSFT, מעניין לשמוע מה הם אומרים.

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

בימים הקרובים אעלה פוסט עם תמונות הסברים רשימות ועוד כרגע מי שרוצה מוזמן להיכנס לאתר של אמזון ולבדוק

Amazon RDS for SQLServer

Amazon RDS - some pictures and explenations....

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

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...
Post a Comment
Read more