« first day (5152 days earlier)      last day (12 days later) » 

00:11
@PaulWhite I learned it from watching you, dad
00:41
REV--;
Check out this parental unit
01:15
@ErikReasonableRatesDarling So often the case
01:30
Happens to the best of us
 
4 hours later…
05:25
4u
 
5 hours later…
10:08
@PaulWhite I said the best of us, don’t drag me into this.
Wordle 1,333 4/6*

⬛🟨⬛⬛⬛
🟩⬛🟩🟩🟩
🟩⬛🟩🟩🟩
🟩🟩🟩🟩🟩
pah
@ErikReasonableRatesDarling It was also a reference to the "4 hours later..."
Wordle 1,333 4/6*

⬛⬛⬛⬛🟨
🟨🟨⬛🟨🟩
🟩🟩🟩⬛🟩
🟩🟩🟩🟩🟩
 
2 hours later…
12:00
Wordle 1,333 4/6*

⬛⬛⬛🟨🟨
⬛🟨🟨🟨🟨
🟩⬛🟩🟩🟩
🟩🟩🟩🟩🟩
 
2 hours later…
13:38
Wordle 1,333 4/6*

⬛⬛🟨🟨⬛
🟩🟨⬛⬛🟨
🟩⬛🟩🟩🟩
🟩🟩🟩🟩🟩
14:15
@PaulWhite Since when did we start adding videos of me in chat
14:39
@SeanGallardy The world has changed
15:01
I'm just a dinosaur
 
2 hours later…
17:32
> A leaked recording on Tuesday revealed the Trump administration’s plans to use AI to help rewrite a large chunk of the federal government’s computer systems.
That should work out great (from here for those wondering)
18:21
@HannahVernon That's gonna be awesome.
...or was I looking for appalling...
Appalling, appealing, is it ireally that different?
18:38
i have a sneaking suspicion that the compilation replay script/optimized plan forcing is doing something with compiled parameter values in query plans
i have another case where it's showing up in a query plan, but the compiled parameter values are not
 
2 hours later…
20:39
@ErikReasonableRatesDarling It does seem the most likely candidate explanation. Will you be able to run a controlled test to determine that as the cause?
Compilation replay, I mean. From memory, your example before did not use a forced plan
I think you're right - I came to this same conclusion yesterday after writing this. Fortunately, I've still got two copies of the database that have not had the table dropped & re-created, so we can check that out to confirm. Thanks for the TABLOCK hint - I'll check that out. Not surprisingly, an earlier version of this code did use truncate table, but it was changed due to an apparent bug in SQL 2019. — CarlDaniel 7 hours ago
That's a new variation on "thanks for confirming"
21:10
@PaulWhite i'm going to mess with that today, just gotta figure out a demo where it kicks in
@PaulWhite v. long winded
Sad to hear truncate table has a bug
on the plus side, it only has one!
(in sql server 2019)
Are you sure or is that a 1% guess
One of the long compilation time demos with outer joins could be a convenient starting point.
Problems with parameter values do seem to be the current theme
21:26
i did a quick search in query store for any queries that currently have the replay script assigned to them
i could only find one system query with a bunch of @_msparams in it
but the compile values are indeed missing!
huzzah
or something
Billions of automated tests
I suppose replay is on by default is it

« first day (5152 days earlier)      last day (12 days later) »