Data Explorer (SEDE)

« first day (2092 days earlier) ← previous day next day → last day (240 days later) »

Aaron Bertrand

01:25

Like a total n00b, I'm going to ask here, how do I edit this page (or any page in the tutorial etc)?

data.stackexchange.com/help

5 hours later…

rene

06:25

@AaronBertrand make a PR to the GitHub repo (like I did here for the tutorial: github.com/StackExchange/StackExchange.DataExplorer/pull/109) and then ask a dev, probably Adam, to merge to master and re-deploy. Allow for 6 to 8 weeks ...

this is the help view: github.com/StackExchange/StackExchange.DataExplorer/blob/…

and the tutorial lives here: github.com/StackExchange/StackExchange.DataExplorer/tree/…

I'm happy to make these changes for you as I have a local SEDE available so I can "test" changes before being pushed to the repo.

Hmm, better link for the tutorial: github.com/StackExchange/StackExchange.DataExplorer/tree/master/…

and help: github.com/StackExchange/StackExchange.DataExplorer/blob/master/…

@rene going forward don't link to obscure commits / branches

rene

07:08

→ 1 message moved to Sandbox/Trash Bin/Something

6 hours later…

Aaron Bertrand

13:18

@rene Thanks! This is useful. Do you have a link handy for the query you used to use to see the status of SEDE refresh?

I have so many tabs open that I really need to clean up today, trust me, it's faster to just ask you. :-)

rene

@AaronBertrand this one: data.stackexchange.com/stackoverflow/query/1239509/…

Aaron Bertrand

You are speedy, thanks!

Aaron Bertrand

13:36

A: How can one see when a query was cached in SEDE?

For an answer to your direct question: How can one see when a query result was last cached in SEDE? One can't. This information is simply not exposed to SEDE. Cached plans and queries are cleared out during every refresh operation, so its age will always be 7 days or less (unless that specific...

2 hours later…

Aaron Bertrand

15:33

I'll have to wait until next week to publish anything about eachdb.

@rene This just came up elsewhere and felt compelled to mention mssqltips.com/sqlservertip/7144/… / mssqltips.com/sqlservertip/7145/…

(Also in my defense I did not write the opening paragraph to part 1. I had to read it three times to understand it, and I'm not sure I succeeded.)

What you won't see on their site :-)

rene

16:40

@AaronBertrand I assumed the SQL team re-implemented FORMAT to be as performant as CONVERT but it look like they literally call out to the CLR. Lesson for today: Always Test for performance, even for things that come for "free" out of the box...

5 hours later…