Viewing blog posts in a specific category.
Posted in Azure, SQL Server on Dec 14, 2020
We have been working in-memory OLTP Technologies to achieve high concurreny. Our platform needs to support about 500 K Concurrent users doing small ( less than 64 KB) reads/writes at high frequency. We have noticed LATCH, LOCK and WRITE Log waits using disk based tables and we are able to avoid those issues using in-memory OLTP in Azure SQL and we are able to achieve the high concurrency.
Posted in Azure, SQL Server on Sep 12, 2018
Learnings from Azure Migration
Posted in Microsoft Technologies, SQL Server on Oct 28, 2017
Simple Stored Procedure for Error Logging
Posted in Microsoft Technologies, SQL Server on Jun 22, 2017
If your business needs the SQL Server to be accessible on public network, you may be very vulnerable for brute force attacks. You need to take safe-guards to protect your valuable assets which is Data.
Posted in SQL Server on Jun 11, 2017
SQL Server Trial Edition Expiration I installed SQL Server Docker Container on Linux Machine running on EC2. I took the AMI Image and launched the existing container and wanted to know when will the SQL Server license expires on Docker container. It expires after 6 Months from initial container launch date.
Posted in Microsoft Technologies, SQL Server on Apr 09, 2017
Our business needs very robust, low latency, highly available and durable online transactional system which supports high concurrency for about four weeks in a year. It's almost like Thanksgiving sale where you mark down very popular item (think of iPhone ) by 100 % . We operate on state level ( K-12 ) online assessment market where entire state takes test in spring for few weeks. To operate in this market , you need to have a robust system which can absorb such a sudden spike in transaction volumes.
Posted in Microsoft Technologies, SQL Server on Sep 20, 2016
Best Practices to follow to make DBA Operations simpler. Practices to follow to cut down troubleshooting time.
Posted in AWS, Cloud Computing, SQL Server on Aug 03, 2016
The first time a DB instance is started and accesses an area of disk for the first time, the process can take longer than all subsequent accesses to the same disk area. This is known as the “first touch penalty.”
Posted in AWS, SQL Server on Jun 30, 2016
These are the steps I followed to enable Native Backup and Restores on AWS SQL Server RDS 1. Created NativeBackupRestore Role and Enabled S3 Bucket Access 2. Created Custom Options Group and enabled to use the NativeBackupRestore Role 3. Modified existing instance to use custom options Group. 4. Successfully Backed up the Database from RDS Instance to S3 Bucket 5. Successfully Restored Native Backups on S3 on SQL Server RDS.