Allowing paging would be huge. Btw, Thank You for rolling out this feature at all! It looks wonderful! Can't wait to try it! However, I won't be able to use it for actual work projects until it supports paging and sorting.3,786 votes
This feature is now complete. For more information on Skip/Take (Limit/Offset), please see the article below.
Thank you for your suggestions and votes.
I would be great to have a standalone version for offline development and unit testing. Something like Storage Emulator.3,787 votes
We’re excited to announce the public preview of the DocumentDB Emulator (https://azure.microsoft.com/blog/documentdb-emulator-for-local-development-and-dotnet-core-support/), which provides a local development experience for the Azure DocumentDB service. Using the DocumentDB Emulator, you can develop and test your application locally without an internet connection, without creating an Azure subscription, and without incurring any costs.
This has long been the most requested feature on the user voice site, so we are thrilled to roll this out everyone that’s voted for it. Please let us know if you have any feedback, questions or suggestions.
It would be great to have some baseline aggregation functions support without having to return all the records and then perform aggregates on them in code.2,611 votes
We’re excited to announce that with the last major service update, we have added support for aggregate functions in SQL. Support for aggregates is the most requested feature on the user voice site, so we are thrilled to roll this out everyone that’s voted for it.
Please see https://docs.microsoft.com/en-us/azure/documentdb/documentdb-sql-query#Aggregates for details.
Need to provide support for SELECT DISTINCT xyz FROM c.1,621 votes
As noted by some comments below, support for DISTINCT is now available. We are working on updating our documentation for this to provide examples and more information. The updated documentation will be published in our SQL query doc here, https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sql-query. Stay tuned, this will be updated soon.
It seems that there is no backup for DocumentDB. You should provide a backup solution for DocumentDB.1,261 votes
Two automatic backups are retained for 8 hour. Please see more here
Document DB should support batch operations in REST API and SDK level. It would be very useful to insert 1000 entities in one transaction.1,210 votes
We released the bulk executor library for .NET and Java this past March that provides support for batch operations. For more information on this feature go to, https://docs.microsoft.com/en-us/azure/cosmos-db/bulk-executor-overview.
DocumentDB offering should provide a free tier for dev/testing.
I'm maintaining the MongoDB provider for NEventStore (https://github.com/NEventStore/NEventStore.Persistence.MongoDB) and would try to build a DocumentDB Persistence Provider.
Would be even better to have an "open source" subscription for oss projects on azure (dev/testing)!1,118 votes
Yes, CosmosDB is available free. Please check https://azure.microsoft.com/en-us/try/cosmosdb/
We need a PowerShell module for managing Azure DocumentDB1,117 votes
Cosmos DB now provides support for PowerShell for all resources including account, database, container and throughput.
For more information see the article below for samples.
Thank you for your suggestion and votes.
Today I have to use JsonProperty or JsonConverter attributes to decorate my objects one property at a time.
This is painful when dealing with large objects and error prone.
It would be a much better idea to support the use of JsonSerializerSettings to set global behavior for JSON.NET ... just like WebApi and ASP.NET does today.1,073 votes
I am looking to convert an application from MongoDB to DocumentDB as I would prefer a managed solution but the collection pricing is absurd. The current model has 1 or 2 collections with 10+ GB of data that will grow at high rates but there are another 30 collections or more with most of them having only 10-20 records. Paying a minimum of $25 per collection is out of the question especially for dev workloads. The pricing model would change your development behaviour to just stuff everything in the same collection but then you loose a lot of the ability to index and know what you are looking at. Until the pricing gets fixed the product is a bad replacement for MongoDB.
I am looking to convert an application from MongoDB to DocumentDB as I would prefer a managed solution but the collection pricing is absurd. The current model has 1 or 2 collections with 10+ GB of data that will grow at high rates but there are another 30 collections or more with most of them having only 10-20 records. Paying a minimum of $25 per collection is out of the question especially for dev workloads. The pricing model would change your development behaviour to just stuff everything in the same collection but then you loose a lot of the ability…976 votes
Database level pricing is now generally available. Learn more about it here, https://docs.microsoft.com/en-us/azure/cosmos-db/request-units
I cannot find any documentation on what order the data from a query will return.
I would love to be able to explicitly specify an "order by" clause to dictate that order945 votes
Please allow partitioned collections with fewer than 10k RU reserved.
I really would like to use partitioned collection but according and the pricing model $6/month for each 100 RU seems fair. But the minimum RU/s for partitioned collections are > 10.000 RU/s which is min $600 a month.752 votes
We are pleased to announce that partitioned collections have an entry point 75% cheaper than before. Instead of provisioning 10,100 RU/sec as a minimum, you can now provision a partitioned collection at 2,500 RU/sec and scale in increments of 100 RU/sec. Partitioned collections enable you to dynamically scale your provisioning from as low as 2,500 RU/sec to millions of RU/sec with no limit on storage consumption.
Please download SDK 1.12.0+ or use the Azure Portal to provision these collections.
Since OData is a standard API supported by Microsoft and intrinsically supports JSON, and DocumentDB is JSON-based, it's a good fit. A standard protocol would also greatly increase interop potential, like SQL, which you are supporting.707 votes
The Table API for Azure Cosmos DB uses ODATA as the primary protocol for querying. See
Applications written for Azure Table storage can take advantage of premium capabilities like provisioned throughput, single-digit millisecond latency, global distribution, and automatic secondary indexing.
I have posted a question in stackoverflow (https://stackoverflow.com/questions/45057385/azure-cosmosdb-mongodb-update-fields-of-an-specific-element-of-an-object-in-an) related to this issue.668 votes
This feature is now available. For more information on this feature and our current supported features for MongoDB API, please see, https://docs.microsoft.com/en-us/azure/cosmos-db/mongodb-feature-support.
Thank you for your suggestion.
Enable DocumentDB in Brazil Datacenter670 votes
We’re excited to announce the availability of Azure DocumentDB in the Brazil South region.
DocumentDB should support Transparent Data Encryption.653 votes
We’re excited to announce that Azure Cosmos DB is now always encrypted in rest. See https://docs.microsoft.com/en-us/azure/documentdb/documentdb-nosql-database-security
Aravind Krishna R.
Azure Cosmos DB
While document ID's are unique, I would like a unique constraint on a given property as well. Today, the only ways I see to accomplish this is either with a client-side query or a pre-trigger (also requiring a query).
I'd like a "unique" constraint to be applicable for given property names within a collection.619 votes
Please check details here https://docs.microsoft.com/en-us/azure/cosmos-db/unique-keys?view=azure-dotnet
From what I see it is impossible to run a query with more than one column in the Order By.616 votes
This feature is now complete. For more information see the article below.
Thank you for your suggestion and votes.
I want a counter is a valid atomic in the collection. Such as use with automatic sequential number.556 votes
We now have support for generating a globally unique Int64 ID with the DocumentID() function.
The function returns a unique number that identifies the document in a collection. The number is extracted from the document’s _rid field. The number is 64 bit long.
SELECT f.id, DOCUMENTID
FROM Families f
However, for an Identity column equivalent for this we are declining this due to scalability constraints. Hopefully this will meet your needs.
Thanks for your suggestion.
Geo spatial support is now available in Azure DocumentDB: http://azure.microsoft.com/blog/2015/08/13/announcing-geospatial-support-in-azure-documentdb
- Don't see your idea?