« first day (5163 days earlier)   

00:07
@PaulWhite we will call you… Paulmost
00:36
Persistence is the key
00:57
Persistence + resistance = THE_REV
 
5 hours later…
06:07
The irresistible force paradox (also unstoppable force paradox or shield and spear paradox), is a classic paradox formulated as "What happens when an unstoppable force meets an immovable object?" The immovable object and the unstoppable force are both implicitly assumed to be indestructible, or else the question would have a trivial resolution. Furthermore, it is assumed that they are two entities. The paradox arises because it rests on two incompatible premises—that there can exist simultaneously such things as unstoppable forces and immovable objects. == Origins == An example of this paradox...
 
1 hour later…
07:20
> When i do this i get blocking and then it gets escalated to chain of bolocking.
2
😆
 
3 hours later…
10:06
Lol. Who said that?
Btw @ErikReasonableRatesDarling are you ok? I got paged at 2 am
@Zikato It's in an old question
I've reached the monthly limit of pages. Erik's health will now be a mystery
Sounds like you need a more expensive plan
Or we need to buy him a wearable and send diagnostic data to some health service with full access. It would help me sleep better - literally
10:09
As a side effect I won't know if my other service that I'm monitoring will be up or down
 
3 hours later…
13:09
@Zikato make it a dog collar to match the way I’m treated around here
13:57
Wordle 1,344 3/6*

⬜⬜🟨⬜🟩
🟨🟨🟨⬜🟩
🟩🟩🟩🟩🟩
14:15
Wordle 1,344 4/6*

⬛⬛⬛⬛⬛
🟨⬛⬛🟨🟨
🟨🟨🟨🟨⬛
🟩🟩🟩🟩🟩
you bring me DUCKS
MALLARDS!@
abominations of the pond
(or lake)
14:37
Wordle 1,344 3/6*

🟩⬛🟨🟨⬛
🟩⬛⬛🟨🟨
🟩🟩🟩🟩🟩
is this a coup d'frog
14:53
i seem to recall some time ago learning that heaps are not eligible for mgr scans
15:05
Oh yes, I remember. I thought that was a true statement at the time.
is it un true
i'm not fighting with this
Yes. There are some things that prevent it on any HoBt, like compression, but as a starting point all types of HoBt (heap or btree) are eligible
huh
what's the beef with compression
no idea
the lack of options for capturing the triggering query text in instead of triggers is quite infuriating
15:10
is it easy for non-IO triggers?
after triggers somewhat yes. you can at least get an idea. instead of triggers just capture the text of the trigger.
using extended events, or some other method?
like input buffer (or the dmv)
inputbuffer, exec_requests, etc.
15:41
well yeah
how's that going
wip?
must be fairly close to finished by now, you'd think
hope burns eternal, like reflux
can't help but rag on their development priorities
16:35
So what was the big news yesterday? Who left to work on elastic search?
Dr No returned
16:59
@PaulWhite don’t even play
18:09
@PaulWhite 😱😱😱
18:41
i briefly went down the rabbit hole of trying to reconstruct the sql statement from what values had changed in the inserted and deleted tables, but that seems mostly pointless
inserts were easy enough
but the where clause of updates and deletes doesn't seem possible
 
1 hour later…
20:10
@SeanGallardy anything in particular? Papers or posts to reference? Asking for a friend. Or more of a "two hard things are harder together" vibe?

« first day (5163 days earlier)