Hemantgiri

With 25 years in the IT industry, I specialize in SQL Server and cloud technologies, holding certifications in ITIL , Azure, and Google Cloud. I have a proven track record of delivering reliable and efficient solutions across various clients and domains.

As a published author, speaker, and community leader, I am passionate about SQL Server high availability, disaster recovery, and capacity planning. I authored a book on SQL Server 2008 High Availability and have delivered presentations at technical events in Surat. Additionally, I founded and lead the SQL PASS Chapter in Surat, nurturing a vibrant SQL Server community.
  • Interests: Reading,Writing,Painting

Blogs

A field note: AI Ambition vs. Operational Reality in 2025

By

Ivan Jelić, Group CEO at Joyful Craftsmen, reflects on what separates AI success from...

Redefining Tech Leadership in the Age of Microsoft AI

By

AI is no longer a niche capability – it is a leadership catalyst. As...

Sample Data with GenAI in Seconds

By

A friend was asking for help with some data analysis. This was in PowerBI,...

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...

do i lose "what this object depends on" etc when moving sprocs to etl server

By stan

Hi i was surprised to see the approach my coworkers used to sunset talend...

People Make Odd Choices

By Grant Fritchey

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

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