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
Consistency Architecture in Azure Cosmos DB
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, then in third Article we talked about Azure Cosmos DB Global data distribution Architecture, today we will complete our series to talk about Consistency Architecture in Azure Cosmos DB For more information about my Azure articles check this link, Keep Following to learn More about Azure and Cosmos DB
Introduction
Microsoft Azure Cosmos DB Provide 5 level of Consistency (Strong, Bounded staleness, Session, Consistency prefix, Eventual) Before Explaining What is Consistency, Why I should take care about Consistency, Which Consistency is best for my APP design before all of that let us talk first about CAP Theorem
SQL Server table partitioning – planning and implementation guidelines
Nowadays, the big environments that have large databases with a heavy amount of transaction they had one common performance issue in the OLTP transaction when the database size increased to the hundreds of gigabytes or more it will be difficult to load data.
Microsoft SQL Server provides us table partitioning to make this OLTP operation more either and manageable. Applying the partitioning on the large table it will split the table and its indexes into the smaller partition, at this time the maintenance procedure can be applied to an exact partition instead of doing it on the whole table. Additionally, the SQL Server engine will direct the filtered queries to the suitable partitions instead of the entire table. All of this will enhance the performance of OLTP transactions significantly. I will list Commons steps for database migration, including the following:
- Concept of table partitioning
- Why we need to implement Table Partitioning
- Table partitioning limitation and restriction
- Table partitioning type
- Table partitioning dependence
- Table partitioning implementation
- Conclusion
- Useful links
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”Partitioning Architecture in Azure Cosmos DB.
Introduction
In my first article in Cosmos DB, I talked about the basic information about How to provision Cosmos DB, and today we will complete our discussion in How Cosmos DB Partitioning work, and What are the Logical Partition and Physical Partition then in the upcoming posts we will talk more and more about Designing and Architecture Layers for Cosmos DB Such as Consistency levels in Cosmos DB Which Consistency levels are suitable with your APP, What are Cosmos API choices, Disaster Recovery and High Availability in Cosmos DB Keep Following ..
- Cosmos DB Physical Partition
- Cosmos DB Logical Partition
- Cosmos DB Partition Key
- How to Choose the Right Partition Key
- Resources
DB Cloud TECH 