Quite a simple requirement (when I needed it a few months ago). Study my Azure SQL database environment below.
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.
While not specific to SQL Server 2019 (I was using this version to do some testing) I was struggling to find how to change the time period of analysis for the Query Store reports within SSMS.
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.
The architecture you could follow is shown below.
It is always a dark art trying to suss out why he/she is an MVP? Do they deserve it? What does it take? Why can’t I get it?
I had a good question from JP via a comment on my blog about whether you can use the MAXDOP query hint in Azure SQL Database. The answer? Yes.
Using Graph DB is a good way to show relationships between entities (more specifically a vertex and edges).
Let’s use the Azure portal to build a globally distributed Cosmos DB. Before doing this, why would you ? what are the benefits?
Technically you do not have to create a cosmos DB and incur costs to test cosmos DB based applications, you could use the local emulator. This means that you do not need an Azure subscription, an actual hosted database or even an internet connection, everything is local to your machine and once ready you can deploy the solution to the cloud.
Cosmos DB falls into the “NoSQL” technology group, call it a buzz word if you like but it is very different to classic Relational Databases such as SQL Server. I never really understood why it was labeled NoSQL, if you build a document based data model via the SQL API you actually use SQL like language to query the JSON (from the collection). Moving on, it is an evolution from what used to exist called Document DB. (Cosmos DB sounds way more aggressive and punchy, right?) Recently I have been using it to store JSON documents (Document based data model) in Azure, as a fully managed service, i.e. PaaS and maybe you will use it one day.