SQL has a lot to recommend it; we've basically built a company around the effectiveness of SQL as a way to interact with data. I will say that it's pretty bad a

SQL has a lot to recommend it; we've basically built a company around the effectiveness of SQL as a way to interact with data. I will say that it's pretty bad at code re-use, and `with` clauses are pretty awkward for breaking down a complicated analysis into small stages. Kusto/Azure Data Explorer [1] is a really interesting new query language, focused on analytics. It fixes a lot of the things that are awkward about SQL. A simple example: StormEvents | where StartTime >= datetime(2007-11-01) and StartTime < datetime(2007-12-01) | where State == "FLORIDA" | count [1] https://docs.microsoft.com/en-us/azure/kusto/query/ https://docs.microsoft.com/en-us/azure/kusto/query/