The weekend feels so far away still.

take a nap

it's like time-travel

Almost the weekend, just a whole day to get through

@J.D. Be careful here, there is a difference between hardening and redo. Typically synchronization will mean hardening of which your answer doesn't say anything about - and no a select will not directly cause an impact to the hardening process.

Their query shows no concept of what "lag time" is, most likely it's REDO given the screenshot but no one knows

2.5h of the weekend has already gone

how sad

4u

@SeanGallardy hmm, good points. I've been out of the AG game for a while now, and a dolphin's brain can only hold so much information. I understand what you're saying at a high level, but I'll probably botch it worse if I try to communicate your point. Any chance you want to edit my answer to include those points?

as I understand it, hardening is when transactions are sent to the secondary, and written to the log, but not yet written to the data file(s).

Redo is taking those new log records and committing them into the data files.

but I also have a dolphin brain, so I'm probably wrong too.

I mean, I use Service Borker regularly, as a case in point.

See, with my dolphin sized brain, I would've assumed by the word hardening, it was the other way around. Good thing I don't manage this stuff anymore 😆

Hannah is right.

Redo is essentially replaying the log records. Kind of like crash recovery on startup, but happening all the time.

Naming things is hard-ening...I guess I see what redo means in this context then. I just would've thought redo meant something along the lines of redo-ing the changes from the primary, primitively speaking, and then hardening is the final commit. But yea I'm just a dolphin.

Good info though, cheers mates!

Hey, dolphins are the second most intelligent creature on the planet.

Humans being third of course.

And Paul White being number one?

exactly, but Paul White's wife though, judging by her Wordle results as of late.

@J.D. no, I didn't;t see it in reddit

Douglas Adams rolling in his grave.

a select query that ran for 19 hours lol - taken from this

"she's a biggen"

sounds like someone could use a young and handsome consultant with reasonable rates

I mean, 19 hours is a long time. I wonder what they did with the results.

gives new meaning to "dashboard in a day"

yes it certainly does

i'm off to lunch with m.j. swart

TTFN~

have a good one

It may have drawn a triangle, but it made up for it with cheerful emoji

LOL at both of you!

@PaulWhite yeah, I was thinking the emoji was an attempt at making me believe the answer was a gooden.

I particularly love that I asked it what prompt I should use, and even with the prompt it suggested, it still didn't even come close.

@ErikReasonableRatesDarling say Hi for me please. I'm a big fan

@ErikReasonableRatesDarling also say Hi for me. I'm his mortal enemy

@J.D. I added my edits, you can roll them back if you don't agree with it.

@SeanGallardy cool thanks! I'll check them out when I get a chance, and will try to learn up more on them thangs!

Crazy busy day today. ☹️

@Zikato @PeterVandivier hellos have been received and returned

I fixed a couple descriptions for XE items. If you all have any other XE descriptions that need fixed or improved please let me know. Unfortunately since 2019 is end of mainstream support it will only show up in 2022+.

I'm making a list and I'll do another round soon

Which ones did you fix

@SeanGallardy thank you for your service!

@ErikReasonableRatesDarling Some ones around HADR of course

Willing to make fixes to others though, just send me the ones and how it can be improved

or just the ones to be improved and I'll try and think of something less sucky

Uh

Can you improve extended events

I can if you give me some ideas

Probably the most useful thing would be event chaining, so you could fire off one event when another event is hit. For example, I’d love to be able to collect query plans for queries when the blocked process or deadlock report is triggered so I can troubleshoot issues better and so I don’t have to source full details from several sources.

It would also be nice to collect the full query text since it’s often cut off in query plans and in the XML representation

Perhaps it would be better if Query Store collected blocking and deadlocks so you don’t have to rely on all sorts of different stuff to monitor problems