database instances


I have a customer that is looking for some recommondation for the following questions. Thank you in advance.

“data base instances. Normally, I run one data base for test, one for production. I have a programmer who wants to run one Tamino data base
roughly per collection. Have you guys found one way versus another that works well? If we put multiple collections into one DB - are there any
drawbacks with regard to utilities (mass loader) or recovery?”

One consideration is that backup/restore are done at the database level.

If you have large amounts of data in one collection you might want to separate it out into its own database so you can backup/restore it separately.

Similarly if you have significant amounts of static data you might want to put them into a separate database to avoid having to back this data up along with your dynamic data.