Why Azure Documentdb creates index on each path by default
问题 By default, documentdb creates an index on every path in a JSON. If we insert a JSON with twenty key-value pairs, documentdb will create indexes on all of these values. Whereas in SQL server, having twenty indexes on a general table is not desirable (especially on transaction tables). So why documentdb does this? Is it because it works on most of the scenarios in documentdb? If So, why? 回答1: Because DocumentDB is designed for schema and query flexibility. DocumentDB is a NoSQL database that