What are the differences between Configuration and Developer Sandboxes?

The Sandbox Documentation describes Configuration and Developer sandboxes, but it’s hard to tell what’s actually different about them:

Configuration Only Sandbox

Configuration-only sandboxes copy all of your production organization’s reports, dashboards, price books, products, apps, and customizations under Your Name | Setup, but exclude all of your organization’s standard and custom object records, documents, and attachments. Creating a configuration-only sandbox can decrease the time it takes to create or refresh a sandbox from several hours to just a few minutes, but it can only include up to 500 MB of data. You can refresh a configuration-only sandbox once per day.

Developer Sandbox

Developer sandboxes are special configuration-only sandboxes intended for coding and testing by a single developer. Multiple users can log into a single developer sandbox, but their primary purpose is to provide an environment in which changes under active development can be isolated until they’re ready to be shared. Just like configuration-only sandboxes, developer sandboxes copy all application and configuration information to the sandbox. Developer sandboxes are limited to 10 MB of test or sample data, which is enough for many development and testing tasks. You can refresh a developer sandbox once per day.

Aside from the difference in data capacity (500 MB for Configuration Only, 10 MB for Developer), what are the differences between these two Sandbox types?

Answer

I think that is the only difference. As Mohith points out in his answer, the difference in data limits has practical implications for how various sandboxes are used.

Attribution
Source : Link , Question Author : Benj , Answer Author : Community

Leave a Comment