Dynobase exports selected items, loaded query results, or a whole DynamoDB table to a local JSON file. Choose the export scope explicitly: current results contain only the rows fetched so far. Whole-table file export reads the table and consumes read capacity.
The demo shows an earlier interface. The written steps describe Dynobase 3.0.8.
1
Choose an export scope
Open the intended table and use Export. Choose Selection to file, Current Results to file, or Whole Table to file; a partial scan is not a complete table export.
2
Choose the file format
Select JSON as the file format. For a whole-table export, choose the local scan-and-save method; S3 export uses a separate AWS-managed workflow.
3
Save and verify
Choose a destination file and let the export finish. Inspect the completion status and the saved data before using it as a migration input or report.
Frequently Asked Questions
How do I export an entire table?
Use Export, then Whole Table to file and choose JSON. Dynobase scans the table independently of the rows visible in the tab; this consumes reads and is not a transactionally consistent snapshot of a table being changed.
How do I export a query result?
Run the query, fetch the pages you need, then choose Current Results to file and JSON. Use Selection to file for a subset, and check incomplete-result warnings before treating the file as complete.
Can I export more than 100 items?
Yes. Dynobase file exports are not limited to 100 items. Whole-table export processes pages; available disk space, data volume, capacity, and operation errors still matter, so verify the result instead of assuming unlimited exports.
What does file export cost?
Saving already loaded results does not require another table scan. A whole-table file export consumes read capacity;
managed S3 export uses separate export pricing and requires PITR.
Can I automate local exports?
Use
scheduled local exports for repeated jobs while Dynobase is running. Review the saved configuration, destination, and job results.
