Microsoft may well catch the rabbit that queries schemas and generates valid SQL. But that rabbit can't understand the meaning of the data just by looking at c

Microsoft may well catch the rabbit that queries schemas and generates valid SQL. But that rabbit can't understand the meaning of the data just by looking at column names and table relationships. Let's say you want to know how sales and inventory are doing compared to last year at your chain of retail stores. Will Microsoft's rabbit be smart enough to know that the retail business is seasonal, so it must compare the last x weeks this year with the same weeks last year? And account for differences in timing of holidays? And exclude stores that weren't open last year? Will it know that inventory is a stock and sales is a flow, so while it can sum daily sales, it's nonsensical to sum daily inventory? The real AI magic isn't generating SQL with four joins, it's understanding the mechanics of each industry and the quirks of your organization to extract the intent from ambiguous and incomplete natural language.