Upskill with Vivek

         Auto scale Azure SQL Database with the help of Monitoring and Automation. Before getting into the auto scale let’s understand that how scaling works in Azure SQL. How scaling works in Azure SQL?            There are 2 type in scaling and that would be decided by Azure. Type 1: The new compute instance will be created with the specified size.   A Replica of that database will be created in the above space, here latency is based on the size of the data base i.e. maximum of 1 GB /minute for coping. During this time the connections will be handled by the previous instance. Then all the connections will be redirected to the new instance. Type 2: The new compute instance will be created with the specified size. The database will be detached and attached to the above. This cause the database unavailability for the maximum of 30 seconds. Enable Auto Scale Here I took S0 tier DB as an exam...

In this article I explained about the Azure SQL Load balance with read only replicas What is read only replicas?                 The replica of the primary database which allows read only access. Secondary replica can be in either synchronous-commit availability mode, or asynchronous-commit availability mode. Availability of read only replicas Availability of read only replicas are based on the tiers. Read Scale-Out is enabled by default on Premium, Business Critical and Hyper scale service tiers. Read Scale-Out cannot be enabled in Basic, Standard, or General Purpose service tiers. Read Scale-Out is automatically disabled on Hyper scale databases configured with 0 replicas. You can disable and re-enable Read Scale-Out on single databases and elastic pool databases in Premium or Business Critical service tiers. Consuming read only replicas We have option to configure the application indent as be...

Explained  the SQL+.Net with a sample project and its steps.               SQL+.Net is the ORM for C# and SQL  designed to complement the skills of SQL developers. By simply adding comments to your SQL you can generate an object oriented class library with good performance. Here is the performance comparison by sqlservercentral.com          Dapper Insert 1000 Records:3364          EF Insert 1000 Records:12794          SQL Plus Insert 1000 Records:2316 Here I have created a console application with sample SQL+ .net ORM utilization. Prerequisites: Visual studio 2017/2019 SQL+.Net Extension – Download the extension in the link -  https://marketplace.visualstudio.com/items?itemName=AHHSoftware.SQLPlusCodeGenerationUtilityDotNetFrameworkVersion1 1. Create a database project Create a table Stored procedures for insert and select ...