The Data Explorer claims that the most recent data is from Dec 7th thru 13th, for all sites.

Last SEDE update

But, it was pointed out to me that this query returns an invalid row (NullUserException earned the badge as of Nov. 15th).

So then I made this query and it claims that NullUserException only has 107 badges, with the latest earned on Nov. 12th.

However, NullUserException actually has 115 badges -- all of them earned well before this latest SEDE update!

So what went wrong with the SEDE data? And, how can we make sure that it won't happen again?


As Conrad Frix points out, none of the data in SO appears to be updated!

I verified this with this query. Indeed, the query on several  other  sites, shows that apparently no data in the SEDE is newer than Nov 13th.

The "most recent" date displays are lies "suboptimal"!


1 Answer 1


I believe this has been resolved - I'd appreciate any testing you can do to make sure this is working properly.

  • Thanks! What was the issue and how will it not recur? Commented Dec 15, 2011 at 21:01
  • Well, it looks like the data has been updated for all the sites (spot checked over 20). But, there are slight discrepancies. EG, SEDE claims that The cooking site's "most recent" data is Dec 13, but it is actually Dec 14. Commented Dec 15, 2011 at 21:01
  • Do all of the datetime columns have indices? As I build up the query, it slows down way more than it should when some relatively small tables are added in. The "Include Execution Plan" option appears to be busted. Commented Dec 15, 2011 at 21:49
  • @BrockAdams I refactored your query here so that it runs Commented Dec 19, 2011 at 3:17
  • @ConradFrix, Ah, I see you made up for the appalling lack of indices on the datetime columns by assuming that the last ID is also the latest timestamp. The the ID columns are all indexed, so this performs well. Good workaround. Thanks! Commented Dec 19, 2011 at 5:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .