2

I have seen that it's possible to explore Stack Exchange data via Google BigQuery as well as via the Data Explorer. What are the benefits of this?

As far as I see, the data explorer is T-SQL, which to me seems an advantage in and of itself. I think (but am not sure on this) that BigQuery can be accessed via an API, whereas I'm not sure that the data explorer can.

Is this the only advantage or are there others?

1

In Google BigQuery, it's easier to combine the tables with other data sources. In SEDE, you're basically limited to what the Data Explorer gives you; external data, including Stack Exchange information that is not exposed, needs to be provided in the query itself via temporary tables and INSERT statements (example).

|improve this answer|||||
  • Thank you @Glorfindel (presumably from Middle Earth?) - when you say 'combine with other data sources'. Do you mean that BigQuery allows you to join completely separate data sources (say GitHub and SE) together? This would be cool – Zach Smith Oct 16 '18 at 6:57
  • 1
    IIRC you can create your own project and use several external datasets (like Stack Exchange and GitHub) in it. – Glorfindel Oct 16 '18 at 6:58

You must log in to answer this question.

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