Skip to main content

About Me

 

Assalamualaikum (peace be upon you).

I am delighted to be part of the core team to design and develop project architecture for Asa Microfinance Management System, which happens to be one of the largest microfinance companies in the world.

I am proud to design relational big data architecture for ASA's 3000+ branches' transactional system with terabytes of database size which is designed to handle at least 15 million transactions a day. Troubleshooting and performance tuning of SQL server with Availability Group for various bottlenecks is not only the part I am good at, but it also happens to be my passion.

I feel like the person responsible for making the SQL server go faster.

Feel free to contact me for your SQL Server Pain Relief, Let me help you find the root cause of your problem! 

I am available to look into your SQL Server bottlenecks. If your SQL Server issue is interesting, I am here to do it free of cost. Just hit the contact me form to get in touch with me.

Comments

Most Loved Posts

Intelligent Query Processing in SQL Server 2019 Big Data

SQL Server 2019: Intelligent Query Processing SQL Server 2019 ships with some brand-new features. Many of these features are targeted for Big Data Solutions. No wonder in that, since the world is moving faster towards Big Data and it is absolutely necessary to cope up with that. Today we will discuss one such feature called Approximate Query Processing. Approximate Query Processing SQL Server ships with Intelligent Query Processing out of the box with SQL Server 2019 installation. Approximate Query processing is a part of Intelligent Query Processing. Things we will be covering in this article – Understand the need for Approximation with Case Study Case Study 1: Railway Case Study 2: e-commerce How to use Approximate Query Processing Demo Code for Comparing Performance Results Limitations When to avoid Approximate Query Processing Understand the need for Approximate Query Processing Before using any technological feature, we must understand why we should use it? Should we jus...