Azure SQL is still 99% the same familiar T-SQL we've been using for decades. Some features like Availability Groups and DBCC commands are gone, because they have been replaced...

Just my dip of the toe into the problem.  I have this thing for making my dynamic SQL look the same as static SQL.  I also used a little trick...

p.s.  I'm probably a minority here but I hate the look of StackOverflow and similar sites.  Everyone has gone that way to support mobile (i.e. smart phones) and so don't...

Understood on not changing the data in the existing column.  It could really screw up a lot of code that's depending on the bloody NULLs.

If you can add a persisted...

Like Jeffrey Williams...

Correct... it doesn't look much different.  It's when you try to use the forum and related functionality.  Their stuff works better than ours do.  Sometimes, ours doesn't work at all.

From my personal observations, "OR" in criteria is more often a problem than not and, with that, I tell people to make their EndDate column NOT NULL and have it...

Here's a simplification of Jonas' method above.

--===== Create the test table and populate it.
     -- This is NOT a part of the solution.
DECLARE...

That show at the end is absolutely awesome.  Thanks, Steve.

DBCC FREEPROCCACHE;

Understand that there could be a period of some pretty high activity and some slowness until all the procs being used are recompiled on their first runs.

BrainDonor beat me to the link he provided.  I'll also add that if you're having serious problems with TempDB, there's usually some code in desperate need of a fix.

Thanks for the info and link.

It looks like the on-premise DBA is going to be met with a few challenges in the future. I know there are a lot...

@steve-2...

No... this is not like stack overflow especially not when it comes to publishing code nor in rendering previous published code (how hard would it be to overcome the quadruple...

I feel like I'm missing something. An inner join is necessarily an existence check, why not:

SELECT u.UserId
  FROM UserTable u
  JOIN TableA a...

You've yet to make the realization that the "upgrade" they did wasn't really user oriented, although I'm sure that Steve will argue with that.  It was to increase the looks...