Looks like it CUs again as...

2019 is finally out for general release: SQL Server 2019 is now generally available

Time to start looking at the specs and what it really includes in the Standard...

To the person with the crystal ball, any prediction...

I'm with Drew on this one. However some observations

Firstly, the relationship between PRData  and TData should be 1-to-many otherwise TData will be repeated many times

Second, GROUP BY will return one...

I wouldn't fetter a machine with replication for something that runs just once per night.  Contrary to what most seem to say, I'd make a linked server, drag what...

What is wrong with using DATEFIRST?

Why the...

What is wrong with using DATEFIRST?

Why the strong negativity?

The default for DATEFIRST is 7 (Sunday)

So

set @dayOfWeek = datepart(dw,@Thur)

will set it to 5 when you want it to be 4

This will return 44 for both dates

DECLARE...

There's been a few games played over here (not that I've seen any of them). I thought they were played at Wembley or the Olympic Stadium.

What "criteria" is it...

• This reply was modified 5 years, 11 months ago by David Burrows.

London has been cited several times for possible Superbowl and the new Tottenham Hotspur stadium was lauded for playability...

Any format containing yyyy-mm-dd can also throw you for a loop if the data had French origins because SQL Server uses YYYY-DD-MM with the French Language.

There is NO WAY...

TF 1118 and 1117 are automatically implemented in 2016.  You can turn them off for all databases except for TempDB.  I wouldn't turn 1118 off anywhere but I would...

I don't think it is possible as Dynamic Data Masking  is applied to column(s) not rows.

One thing to try is to create view that does your own masking of columns...

To really help we need CREATE AND INSERT statements for the tables and what is the expected output for the data supplied.

However this might get you going

SELECTStockCode
FROM(SELECTw.StockCode,w.Warehouse,MAX(w.DateLastSale)
FROM#InvWarehouse...

I am not aware of a single copy causing this unless it is propriety.

I know DOS COPY using + to concatenate files certainly does (and always has done)

ie COPY file1+file2...