Kunal Rathi

With more than 13 years of experience in data engineering and analytics, I've assisted countless clients in gaining valuable insights from their data. As a dedicated supporter of Data, Cloud and DevOps, I'm excited to connect with individuals who share my passion for this field. If my work resonates with you, we can talk and collaborate.
  • Interests: Data Warehousing, Data science, Machine Learning, Big Data

SQLServerCentral Article

Manage Elastic jobs in Azure using Azure Elastic Jobs Manager

Microsoft Azure offers Azure Elastic Job agent as a managed service, enabling efficient scheduling of T-SQL workloads on Azure SQL Databases. Learn how to configure the service in this article.

5 (2)

You rated this post out of 5. Change rating

2024-06-07 (first published: )

1,430 reads

Blogs

TSQL Tuesday #188 Growing community

By

I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...

Time to Revive our YouTube Channel

By

It’s been forgotten about and neglected for few years but I’ve decided to dust...

Microsoft MVP 2025: Continuing the Data Platform Journey

By

I am honored to announce that I have been renewed as a Microsoft MVP...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

People Make Odd Choices

By Grant Fritchey

Comments posted to this topic are about the item People Make Odd Choices

SQL Server 2022 Clusterless Distributed Availability Group

By Pablo Echeverria

Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...

Visit the forum

Question of the Day

Query Plan Regressions --

For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question:  You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?

See possible answers