Distributed Tables in Azure Synapse SQL

Azure Synapse is the new Generation of SQL DW (Azure SQL Data Warehouse), that is launched in the past year In November 2019 the First announced for Azure SQL Synapse was in Microsoft Ignite 2019, With Azure Synapse you can bring together cloud data warehousing and big data analytics into a single service platform, Azure Synapse is massively parallel processing (MPP) Engine. Microsoft Added on it many features, With Azure, Synapse Compute is separate from storage, this means you can scale compute independently for the data in your System (APP), With Azure synapse, you can bring the relational Data and Non-relational data together in one place and easily you can do your query and your analytics on a huge amount of information, Azure Synapse build for a massive parallel query for Analytics not for transaction database, Azure Synapse uses Azure Data Lake Storage Gen2 for more information About Azure Data Lake Gen2 Check this Post, Azure Synapse Support (Apache Spark integration, Power BI, Azure ML), Also you can take a look to this demo with Rohan Kumar this demo is part from Microsoft Ignite 2019 Keynote and you can Follow Rohan Posts from here

Continue reading “Distributed Tables in Azure Synapse SQL”

Azure Cosmos DB Global data distribution Architecture

In my first article in Azure Cosmos DB, we talked about What is Cosmos DB and How to provisions it, then in the Second article we talked about Partitioning Architecture in Azure Cosmos DB. And today we will complete our learning to understand What is global distribution in Azure Cosmos DB? For more information about my Azure articles check this link

When we say global distribution you Should think Automatically in Cosmos DB because it is the most solution in the market provide this feature global distribution, But why global distribution we should be interested in it for couple of reasons unlimited elastic write and read scalability, Yes Cosmos DB provides a solution to read and write option in multiple regions most of the databases solutions provide read scalability but in Azure Cosmos DB we have also write scalability.

Continue reading “Azure Cosmos DB Global data distribution Architecture”

SQL Server Stretch Database to Azure

One of the interesting feature announced in SQL Server 2016 and later to move your cold data to Azure and the data will be accessible from your APP with ZERO development cost no change in the APP level at all and no change on the Query level in SQL Server it is just configuration and implementation for Stretch Database from on-premises to Azure, IF you are DBA and you have tables with big size and you need to reduce it, if you have Cold data and the APP not accessing it frequently, If you need to reduce the backup and restore time at this time this feature for you.

Before starting on the benefits of this feature and How to implement it I highly recommend you to take a look into this page to learn more about Azure SQL https://lnkd.in/edn6nyY/#AzureSQL

  • Benefits from SQL Server Stretch Database
  • How to Configure the SQL Server Stretch Database to Azure
  • Validate the Database Stretch configuration and Data movement
  • How to Disable the Stretch data
  • References
  • Keep Following
  • Cloud Tech Website blog survey
SQL Server Stretch Database
Continue reading “SQL Server Stretch Database to Azure”

Azure SQL Database Tiers Options

Microsoft azure providing multiple options for Azur SQL Database Tier, supported Azure Single Database, Azure Elastic Database, and Azure managed instance before starting for what is the options and the details of it if you need to learn more about Azure SQL provisioning, security, High availability, Performance, …etc. check this link you will find very useful articles covering the most basic topics in Azure SQL Database. ➡️ https://lnkd.in/eABFfrs 💨✅ Today I will start to explain the Purchase mode and database tiers related to Azure SQL Single, Azure SQL Elastic Database and Azure SQL Manged instance.

Azure SQL Database Tiers
  • Azure purchasing models
  • Azure SQL Single Database Tiers Options
  • Azure Single Database Tiers on DTU-Based
  • Azure Single Database Tiers on vCore-Based (GP)
  • Azure Single Database Tiers on vCore-Based (Hyperscale)
  • Azure Single Database Tiers on vCore-Based (Business Critical)
  • Azure Elastic Database Tiers Options
  • Azure Elastic Database Tiers on DTU-Based
  • Azure Elastic Database Tiers on vCore-Based
  • Azure SQL Managed Instance Tiers
  • References
  • Keep Following

Azure purchasing models:

Microsoft Azure supported two Purchase model:

  1. DTU-Based Model: Supported Azure SQL Database only
  2. vCore-Based Model: Supported Azure SQL Database and Managed instance

For more information check this article

Azure purchasing models
Continue reading “Azure SQL Database Tiers Options”

Azure Cosmos Database Basics


Azure Cosmos Database one of the Non-Relational NoSQL Database provided by Microsoft and we have another NoSQL Options in Azure like (Data Lake Storage Gen2, Blob Storage, Redis Cache, HBase in HDInsight), also Azure Cosmos Database Supported multiple API like (Core SQL, Mango DB, Cassandra, Graph, Azure Table) IF you need to learn more about this Point Check this Link Choose the appropriate API for Azure Cosmos DB, Azure Cosmos Database supported Write option in multiple regains in the same Database and the synchronizations tacking care about syncing the data. For more information about Azure Cosmos database, I highly recommend you to look into Microsoft Documentation

  • How to Provision Azure Cosmos DB Account
  • How to Provision Azure Cosmos DB Container
  • Load and Explorer the data into Azure Cosmos DB Container
  • Replication in Azure Cosmos DB
  • Data Consistency in Azure Cosmos DB
  • Cosmos DB and open Source
  • Azure Cosmos Database Resources
Cosmos DB NoSQL

How to Provision Azure Cosmos DB Account

To Create Azure Cosmos Database we need to create First Database account and this like Database instance we can host on it multiple databases, then after this step, we need to create Container ID and this the Database name in this you can find below what is the information required when we need to create Azure Cosmos Database account and for how to do it check below 👇✅ GIF File ✅to know how you can do it and For more information Check this Article

  • Account Name: it is like the instance name in SQL Server
  • Notebooks: Jupyter notebook is an open-source web application that allows you to create and share documents it is like the Azure Data Studio Notebook For more information read this Article
  • Location: The location you need to host on it your Azure Cosmos DB account
  • Account Type: It is something like a definition or categorized, we can consider it like Azure Resource Tag.
  • Geo-Redundancy: Enabling this Option automatically replicates your data to the region geo-paired with your current region you selected it. For more information about the Region geo-paired check this link Azure Regional Pairs IF you don’t enable it during the setup you can enable it after the configuration from the main overview of the Azure Cosmos Account
Enable Geo-Redundancy
  • Multi-region Write: Enable the write option on the Regions you selected it on the geo-redundancy this means If you need to enable the Multi Regions Write option you Should Enable the Geo-Redundancy option with it this option you can enable it after the installation from Replicate Data Globally option If you need to learn more about this option check this Link

Continue reading “Azure Cosmos Database Basics”