« first day (2091 days earlier)      last day (242 days later) » 

01:14
Found some time this evening to make this better still:
22
A: Create a view that provides a list of databases

Aaron BertrandI've built something you will hopefully find useful, as it will present a list of databases (and a bunch of additional information) that you can use for cross-database queries. Before I explain further, though, I'm going to start with some caveats: Caveats Due to the principle of least disrupti...

Added dbo.sede_users - hitting the hay now but AMA
I'll respond tomorrow, maybe.
I've left plenty of examples so you can try it out in the meantime.
 
9 hours later…
09:54
10:35
@rene Nice! I will probably borrow from that for an example
...if that's ok
sure! Go ahead.
 
1 hour later…
11:53
@AaronBertrand there are some weird rows in there where reputation is 0: data.stackexchange.com/stackapps/query/1836188 as those has a site_id that isn't present in sede_sites I assume that is due to closed/sunsetted sites. sede_users might need an extra condition to filter those out.
12:07
Thanks! Should be fixed now
There are still some rows with zero reputation, possibly they haven't had a rep-recalc in a long time or are otherwise missing from the aggregated network-wide tables.
I'll change the view to output 1 in that case instead of 0.
 
7 hours later…
19:04
Ok, it's not pretty and may be hard to grok in a single pass, and it takes 30 seconds, but this demonstrates some power I think:
https://data.stackexchange.com/stackoverflow/query/1836260/top-50-accounts-by-network-rep-plus-their-top-post-from-their-best-site
19:32
wat
0
Q: How can one see when a query was cached in SEDE?

Franck DernoncourtQuery results in SEDE are cached: How can one see when a query result was last cached in SEDE?

@Feeds closed as a duplicate that I knew existed
@AaronBertrand that is pretty need!
@Feeds it might be that with the new SEDE refresh logic the query cache isn't reset any more? /cc @AaronBertrand (if so we can re-open it for an answer)
20:33
I don’t think so, it actually wipes them out too often during each weekend’s refresh (it’s called after each database, which you might see in one of Nick’s gists).

« first day (2091 days earlier)      last day (242 days later) »