Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

50%
+1 −1
Q&A Migrating from Az Co DB NoSQL to Az Co DB MongoDB, error?

From my own trial and error the solution was to temporarily increase the Read Units Per Second for the MongoDB. Then it worked flawlessly the first time to import.

posted 8mo ago by propatience‭  ·  edited 7mo ago by propatience‭

Answer
#3: Post edited by user avatar propatience‭ · 2024-05-27T09:30:01Z (7 months ago)
  • From my own trial and error the solution was to temporarily increase the Read Units Per Second for the MongoDB. Then it worked flawlessly the first time to import.
  • And also later I've increased Read Units per second and I've used MongoDB Compass for data migration and it worked very good also. MongoDB Compass migration guide:
  • To use and connect with MongoDB Compass, please look here
  • https://www.mongodb.com/products/tools/compass
  • https://www.mongodb.com/docs/compass/current/connect/
  • MongoDB Compass, Export Data
  • Inside MongoDB Compass
  • Click on the source collection, for example database &lt;your source database>, collection &lt;your collection>
  • EXPORT DATA
  • Export the full collection
  • JSON
  • Export...
  • In your Downloads folder or another temporary folder, save the file
  • Increase RU/s for MongoDB
  • Log in to Azure Portal
  • Find and click on &lt;your cosmos db>
  • Data Explorer
  • &lt;your target database>
  • Scale
  • Manual
  • 10000
  • Save
  • MongoDB Compass, Import Data
  • Inside MongoDB Compass
  • Click on the target collection, for example database &lt;your target database>, collection &lt;your collection>
  • ADD DATA
  • Import JSON or CSV file
  • In Downloads folder or another temporary folder, Select your exported file
  • Stop on errors: True
  • Import
  • Decrease RU/s for MongoDB
  • Log in to Azure Portal
  • Find and click on &lt;your cosmos db&gt;
  • Data Explorer
  • &lt;your target database&gt;
  • Scale
  • Manual
  • 400
  • Save
  • Delete Data File
  • In Downloads folder or another temporary folder, Delete your exported file
  • From my own trial and error the solution was to temporarily increase the Read Units Per Second for the MongoDB. Then it worked flawlessly the first time to import.
#2: Post edited by user avatar propatience‭ · 2024-05-27T09:25:51Z (7 months ago)
Updating with MongoDB Compass migration guide
  • From my own trial and error the solution was to temporarily increase the Read Units Per Second for the MongoDB. Then it worked flawlessly to import.
  • From my own trial and error the solution was to temporarily increase the Read Units Per Second for the MongoDB. Then it worked flawlessly the first time to import.
  • And also later I've increased Read Units per second and I've used MongoDB Compass for data migration and it worked very good also. MongoDB Compass migration guide:
  • To use and connect with MongoDB Compass, please look here
  • https://www.mongodb.com/products/tools/compass
  • https://www.mongodb.com/docs/compass/current/connect/
  • MongoDB Compass, Export Data
  • Inside MongoDB Compass
  • Click on the source collection, for example database &lt;your source database>, collection &lt;your collection>
  • EXPORT DATA
  • Export the full collection
  • JSON
  • Export...
  • In your Downloads folder or another temporary folder, save the file
  • Increase RU/s for MongoDB
  • Log in to Azure Portal
  • Find and click on &lt;your cosmos db>
  • Data Explorer
  • &lt;your target database>
  • Scale
  • Manual
  • 10000
  • Save
  • MongoDB Compass, Import Data
  • Inside MongoDB Compass
  • Click on the target collection, for example database &lt;your target database>, collection &lt;your collection>
  • ADD DATA
  • Import JSON or CSV file
  • In Downloads folder or another temporary folder, Select your exported file
  • Stop on errors: True
  • Import
  • Decrease RU/s for MongoDB
  • Log in to Azure Portal
  • Find and click on &lt;your cosmos db&gt;
  • Data Explorer
  • &lt;your target database&gt;
  • Scale
  • Manual
  • 400
  • Save
  • Delete Data File
  • In Downloads folder or another temporary folder, Delete your exported file
#1: Initial revision by user avatar propatience‭ · 2024-04-26T08:19:12Z (8 months ago)
From my own trial and error the solution was to temporarily increase the Read Units Per Second for the MongoDB. Then it worked flawlessly to import.