[external] Populating a new configuration database from an existing one

External content by Daniel Krüger; June 10, 2024 ; 
The original post has appeared on daniels-notes.de

If you ever encountered a situation where you needed to install a new environment and already had an working environment you may have wondered, how you can make sure, that everything has been setup the same. 
While this is easy for the global parameters, there are other artifacts where the sheer number of elements makes this hard.

Therefore I described my approach to create this checklist using the configuration database table.
In the end I considered the following artifacts:

1. BPS Groups: Need to be transferred.
2. User profile and favorites: Can be ignored.
3. Registered API applications: Need to be transferred.
4. Devices: Can be ignored
5. Licenses assignments: Need to be transferred since subscription licensing is used.
6. Substitutions: Can be ignored
7. Themes: Need to be transferred

The blog post provides information about the available options and sometime other helpful information.

READ MORE: here.

In case you are interested in copying a content database you find more information:

• https://community.webcon.com/posts/post/mirroring-environments-for-2023-standalone/427/3
• https://daniels-notes.de/posts/2023/copy-a-database