Sometimes you may not want to flip over to the Azure portal to grab the database size, such as the used space below.
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.
You can read about columnstore indexes here (https://azure.microsoft.com/en-gb/blog/transforming-your-data-in-azure-sql-database-to-columnstore-format/). I won’t rehash the material but high level, these index types are optimized for analytical queries and high compression of data (up to 100x). This format is perfect for the large data sets that can be efficiently compressed using this format and analytical queries with complex calculations that use subset of the table columns.
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.
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.
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.
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?