My current focus is directing and managing strategic and operational aspects of Pragmatic Works, a data services organization focused on democratizing analytics and data related technologies. I built the organization from the ground up (with my co-founders) to include industry leading processes, attract and retain top industry resources and execute powerhouse partnerships with firms like Microsoft and HP to deliver the highest quality solutions in the most innovative ways.

All authors

All authors

Blogs

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

TSQL Tuesday #188 Growing community

By

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

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