Microsoft and Oracle recently announced a joint cloud partnership (I have seen the word multi/cross-cloud to explain this) which I found very fascinating to read. It is currently in preview and the idea is to have an integrated cloud experience between Oracle Cloud and Microsoft Azure. A private dedicated connection is obviously needed and whilst knowing more about Azure, looking at the below diagram it makes sense (from an architecture POV) as the Oracle equivalent of ExpressRoute is FastConnect which is needed.
I was generally reading about SQL Server and how things have changed since the days of just having it within a Windows Eco-system only. It then led me to a cool website, SQL Server development – build an app using SQL server where you can get to see the high-level requirements of starting to build a solution based on a wide variation of languages and operating systems. https://www.microsoft.com/en-us/sql-server/developer-get-started/
There are many combinations possible with SQL Server being the back-end database of choice.
There is a lightweight and quick way to start querying your database in Azure which doesn’t involve SQL Operations Studio or Management Studio. You can use the query editor within the Azure portal, that is, if you desire.
I am sure many missed the updates to Azure SQL Database SLA (Service Level Agreement). It used to be 99.99% across all tiers but split between two different high-availability architectural models. Basic, Standard and General Purpose tiers had its own model and the Premium / Business Critical tiers had a different one.
The purpose of an Elastic Job is to execute a T-SQL script that is scheduled or executed ad-hoc against a group of Azure SQL databases. Targets can be in different SQL Database servers, subscriptions, and/or regions. This blog post is quite long and heavy (code wise) so grab a coffee and follow through.