« first day (5003 days earlier)      last day (20 days later) » 

7:42 AM
> Invalid use of a side-effecting operator 'BEGIN TRY' within a function.
Invalid use of a side-effecting operator 'PRINT' within a function.
 
2 hours later…
9:47 AM
Wordle 1,184 5/6*

⬛🟨⬛⬛🟨
⬛🟨🟨🟨⬛
🟨⬛⬛🟨🟩
⬛🟩⬛🟩🟩
🟩🟩🟩🟩🟩
Nostalgia
 
1 hour later…
10:59 AM
@PaulWhite what a cutie patootie
My word the docs for SET has better cursor documentation than the docs about cursors
So weird. Looking for the properties window in 2000 plans, or right-clicking to get the XML
It aint there
Nothing. What you see is what you have
Also what the hell are you doing looking at 2000 plans
I wanted to see if something worked on 2000
I became distracted
Honestly, I don't remember now. It wasn't all that important
Currently reading about using the T-SQL debugger to troubleshoot stored procedures 😭
In the high-speed local documentation
Oh, I remember what I was doing now. Yes, the repro worked on 2000 RTM
It was a Halloween Problem bug, long since fixed
A lovely merge join
Those sorts are 🤌🍕
Well, I did hint MERGE JOIN
And INDEX(0)
There you go. Just one input sort
Back in the days when SHOWPLAN_ALL was the last word in plan detail
11:21 AM
Wait was there parallelism then
Yes, introduced in 7
2000 added quite a few things though, like bigint and UDFs
Oh sorry I meant for plan indicators
indexes on computed columns, xml
Yes, well, Ken Henderson walked the earth in those days
Good things happened
@ErikReasonableRatesDarling Yep ^
11:26 AM
Neat
Thank you
No SSMS back then. Two separate apps, one for server management and one for queries
Before my time. First version was 2005.
I started on 6.5
Seemed cool at the time, but it was horribly limited
You'd better enjoy nested loops joins, for example
2000 also added indexed views and the ability to run multiple instances
Oh, and table variables
Before 2000, only stored procedures and triggers reused execution plans
11:44 AM
Huh
2000 was a great release then
Huge. Second only to 7 really
Think so
2005 was epic as well
But nothing beats 7
What does it for you about 7?
Almost a complete product rewrite. The optimizer arrived
Pretty much everything good about SQL Server has its roots in 7, if it wasn't created at that stage
Parallelism, row level locking, hash joins...you name it
11:49 AM
Neat
I do think SQL Server releases were pretty solid up until 2012
The product actually seemed to move meaningfully forward
I suppose 2000 was largely finishing bits of work that didn't fit in 7
@ErikReasonableRatesDarling Yes
2008/R2 was a bit of a blip along the way
Necessary to bring in more licensing money
Maybe 2008 had some good stuff, but R2 was a service pack
Hm
Compression? That was 2008.
Oh the date data type, hahaha
The documentation for 2000 is awesome
There's a whole library section on cursors, for example
11:59 AM
Post it somewhere!
Everything is worse in the cloud, BOL docs learn
I mean, just look at it all
That's just a tiny fragment of BOL ofc
I do remember the local help files
Most of the cursor pages still exist now, or are accessible online via the retired documentation, but it's a pain to find and read because it's so scattered
One could do heaps of really productive learning just by flicking through BOL
And this is back when KBs were fully documented with repro code and internal details
We've really gone backwards there
Yes the decline in any sort of care is astounding
This is the KB I was reading earlier, for example: betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/…
Naturally, Microsoft have deleted it so it's on an archive site
Most fixes now don't even get an article of their own, just a vague paragraph
12:09 PM
Wow
lol paragraph
2kind
Well, yeah, often it's just a sentence
> Fixes incorrect results for queries that filter on ROW_NUMBER and involve nullable columns.
I would punch whoever decided that was sufficient
Someone somewhere is proud of that sentence
I expect their LI profile is built around it
their life is probably lots of sentences like that
imagine working with them
poor erin
12:28 PM
defrag.exe
I don't want to give ol' Bob there a hard time, but shouldn't a Team Lead be able to write a coherent paragraph
oh hang on
hold up!
just u w8
record scratch
lemme blow your mind
fuck me, we're doomed
also 🤯
> what subjection do you have?
your honor i subject
12:37 PM
the second reply is just astounding
made belief babble
I wonder if his middle names are Lakhing and Any
I suppose a diverse world requires people along every point of the curve
Anyway
This is what you get for encouraging comments
I may need to take the Advanced Optimism class
Because that's just depressing as all Hell
i think you just need a subscription to beer gut magazine
1:09 PM
One can only dream of such riches
this month's issue promises to be a masterpiece
Can't wait!
1:28 PM
i've been offered 20% off my next food delivery, up to $3.50
that doesn't seem like a very good deal
1:53 PM
@ErikReasonableRatesDarling what's with all the armless guys
Wordle 1,184 4/6*

⬛⬛🟨⬛⬛
🟩⬛⬛🟨⬛
🟩⬛🟨⬛🟨
🟩🟩🟩🟩🟩
as your ai overlords
2:19 PM
they're mostly 'armless
i was trying to find all the questions where someone deleted their answer after a paul dunk answer
but i think the schema is annoying
and i'm not sure if i can differentiate self deletes from mod/vote deletes
 
2 hours later…
4:07 PM
8
Q: SQL Server: how Row Goal affects the same index operation?

Jan DrozenI am tuning some SQL performance in the SQL Server 2019, and I ran into issues with one query that involves the issue with the row goals. The simplified query is: select TOP 1 ISNULL(RUNID,-1) from T_PROCESS_MONITOR mon WITH (INDEX = IDX_T_PROCESS_MONITOR_RUNID) WHERE mon.SOURCE = 'Dynam...

actually sort of an interesting question
 
8 hours later…
11:55 PM
@ErikReasonableRatesDarling Erik has the guts to wear a beer gut t-shirt without the actual beer gut

« first day (5003 days earlier)      last day (20 days later) »