Add ability to rename databases and collections
It should be possible to rename databases and collections.
This feature is universal in all if not the vast majority of database products.
Lack of ability to rename anything makes it very hard for us to manage releases if we are adding new data. Currently, we have to create a copy of the existing database (which is a feat in itself, since this again is not core functionality), make the change there, and then re-point the website to the updated database. All this time, we are incurring extra costs and inconvenience.
Renaming things also allows us to correct typos, which happen from time to time!
The ability to rename databases and collections is not currently something that is in our road map.
Currently the way to accomplish this task in Cosmos DB is to create a new collection with the changed name then use bulk exec or change feed to populate it.
Thanks for your request and input on this. We may consider this for a future planning cycle.
Chandan Gupta commented
When will this feature be in product roadmap? We accidentally had "." in the name and now datafactory linked service cannot connect the database. :(
They haven't figured out a way to monetize the rename yet, outside of forcing the use of bulk exec which sets your RU/s through the roof and leaves them there to maximize your bill
Marko Oja commented
"yes, we are also looking for this feature. we need to write to a new collection and once successful, we are planning to delete old collection and rename new to old. since azure search is configured to search the old collection"
We have exactly the same need. Please reconsider this valuable feature for enterprise architecture solutions.
How is this BASIC functionality not available 2+ years later from the original post?
PLEASE ADD THIS BASIC FEATURE
Imre Pühvel commented
It doesn't even have to be a true rename of the same resource (which obviously could be complicated), but some tested comfortable migration automation, with suitable disclaimer regarding risks and most likely a small downtime is expected., would significantly reduce possible mishaps during manual resource reorganization.
Can we have this already? :)
yes, we are also looking for this feature. we need to write to a new collection and once successful, we are planning to delete old collection and rename new to old. since azure search is configured to search the old collection