Jeff's question is really an open issue.  As written the requirement isn't clear so what does "not working" mean?  The predicate should already exclude values with two or more dots:

This is an ancient topic.  Doesn't matter to me tho.  Looking through these answers I don't see one I like.  The LOWER() solutions express the test indirectly.  The _CS_ collations...

It seems reasonable to infer there was a detailed prompt...

Claude's a prickly pear. I've found...

Afaik if the column list is variable it's not possible to unpivot without dynamic SQL.  On a per table (or schema) basis if the columns are known then you could...

Yes that answers it.  It seems possible to create an iTVF per table/schema (if it's hard coded explicitly referencing columns and table(s)) that gives users what they're looking for.  Not...

The design is annoying but maybe not unfixable if you could encapsulate access (queries, views, etc.). Imo the bigger issue is whether the table(s) store when things happened (datetime per...

Hi Pieter,

Once you unpivot into (Symptom, Grade, Causality, Relatedness) you’ve gotten rid of the original “slot” number (the 1, 2, 3 suffixes). Maybe that matters? It might if you later...

Maybe the issue is the query could possibly be more efficiently evaluated if expressed as two queries.  It always depends on the actual situation with cardinalities and indexes etc.  If...

1.  It's not allowed.
2. SQL Server wants to guarantee a single parent delete cannot reach the same target row by more than one cascade route.  Multiple cascade paths are not...

Sure redesign if possible.  As far as the task at hand it depends on the number of rows really.  If there are a good many rows then allocating a temp...

Ha yeah I was reluctant to test it out.  Sorry for the syntax issues.  Originally I had a table CREATE statement but then switched to SELECT INTO because that's more...

How about creating a giant temp table from a CROSS JOIN using 2 fnTally functions.  Then join the temp table to itself forcing a HASH JOIN with tiny memory grants...

Assuming this is dev or the table is empty, DROP and recreate with the proper column type and default.  Something like this

drop table if exists dbo.latest_info;
go
create table...

You're looking to set the DEFAULT value of the publish_date column to be the current Unix timestamp?  If so the proper column type would be BIGINT.  SQL Server’s native datetime...