Managing Ensemble
Separate Databases for Routines and Globals
[Home]  [Next]
InterSystems: The power behind what matters   
Class Reference   

Separate Databases for Routines and Globals
When you create a new namespace, you specify the databases that contain routines (the code) and the globals (the data). For new namespaces, InterSystems recommends that you specify different databases for routines and globals. Many existing namespaces use a single database to store both routines and globals. Although it is possible to split such a database into two separate ones, it is typically not worth the effort, which includes copying the routines from one database to another.
Some Ensemble classes, such as Ens.Production and Ens.Rule.Rule, can be updated dynamically but are stored in the routines database. Consequently, if you are mirroring the dynamic data in an Ensemble namespace, you should include the routines database in the mirror.
You should always compile the production on the system that it is running. Although you can compile Caché code on one system and copy the database “pre-compiled” to another system, you should not attempt this with Ensemble namespaces.