Very interesting.  It looks impressive and the site works great.  The GitHub repo (+1 star'ed) is always the interesting part imo.  It seems maybe the project began a while ago...

You could nest the current formula inside an additional CONCAT function and test for the existence of the lead characters

 SELECT  tt.homepage_url
    ...

• This reply was modified 3 years, 10 months ago by Steve Collins. Reason: LEFT(String, 4) is a better comparison than CHARINDEX

Does the query return the expected output?

One place to keep important SQL-related information for me is SSC's Briefcase feature.  For a while after I became a member it wasn't working (at least for me using Chrome...

Avoidance is the easy way imo

ORM only makes sense if the mapping is necessary, no?  Otherwise, if it's easier to not use ORM then it becomes a waste to use it.  Imo since .NET 6...

IQP is important because there are more processes reading the database, not all of them written by developers.  Some are generated by reporting tools or ORMs.  This sort of...

with rn_cte as (
    select *, eow-[Week] wk_diff,
           row_number() over (partition by it, cg,...

In Visual Studio if you hold the Alt key down while using the mouse to highlight text it rectangularly selects areas.  Because the dates are horizontally aligned with just a...

No comment on the date calculations?

declare @start_yr           int=2022;

with months_cte(mo_num) as (
    select * from...

Why store information which is derivable by query?  It sometimes creates race conditions keeping updated.  If you're looking for performance you could try splitting the clustered index away from the...

Here's a query with some date calculations.  The value calculated in CROSS APPLY is the difference in days between the customer's DateofJoin and the order's DateVal.  Based on this difference...

The data contains a duplicate row.  How to handle duplicates?  Also, VID is nullable so are NULLs to be ignored or treated collectively as a VID?

Once they realized the mistake, they attempted to soften the blow by creating DATEDIFF_BIG.  A valiant attempt that works nicely except for the rather obvious and unfortunate fact that...

You could divide the rows using two queries: one above and one below UNION ALL. Above SELECT ID's with [type]='Alias' and below SELECT ID's without any 'Alias'.  You could assign...