Very good article to explain the basics.

I think it is important to have Part II for such an article, raising topics like CQRS, where SQL is used for Create /...

Understood - this is live data and users perform CRUD commands 24/7.

likely the standard method of inserting into a new table with the column being calculated at that stage, and then one of 2 options

1 - truncate source table (remove...

• This reply was modified 2 months, 1 week ago by  BOR15K.

Interesting... 5 years down the road and I have the same issue with Azure SQL. Any suggestion, please?

DECLARE @stmt nvarchar(max);  
DECLARE @params nvarchar(max);  
EXEC sp_get_query_template...

I found a suggestion on another site (not sure I am allowed to mention here), which is based on sys.dm_db_tuning_recommendations table:

WITH DbTuneRec
AS (SELECT ddtr.reason,
   ...

It is a bit scary to...

Thank you for the comments. I am more concerned with Prod update. Providing Dev / Test passed with no issues, what are the steps to amend the compatibility in Prod...

That was my first step. Done already. But I presume there are challenges on the actual update, especially in Prod, with 100's GB...

Take a look at Hierarchies on Steroids #1: Convert an Adjacency List to Nested Sets & Hierarchies on Steroids #2: A Replacement for Nested Sets Calculations from...

List of various Ids: document ids, booking id etc. Those in turn have their respective tables.

Thank you for such a detailed reply. I have just noticed I wrote 500MB instead of 500GB - mia culpa and I apologise.

My experience from SharePoint from two last places...

Thank you all for your help and suggestions.

Thank you all for the valuable replies, but I think this discussion diverted from my original question: why my tally table's function had worse execution plan than my...

Thank you all for the valuable replies, but I think this discussion diverted from my original question: why my tally table's function had worse execution plan than my colleague's simple...

Thank you, Jonathan. Almost every step in the execution plan now marked as "No Join Predicate" and the whole function now costs 100% with my original tally one costing 0%