Question
Non Prod Database Consolidation
We are planning to perform Database consolidation by allocating only one database instance for all NON-prod environments and rename the schema's based on the environments.
For example, (PEGA_RULES_DEV, PEGA_DATA_DEV) (PEGA_RULES_SIT, PEGA_DATA_SIT), (PEGA_RULES_UAT, PEGA_DATA_UAT), (PEGA_RULES_PREPROD, PEGA_DATA_PREPROD).
Please advise us whether this is feasible? Would there be any concerns? What are the configuration changes required for this approach. Has anyone tried this before?
***Edited by Moderator Marissa to update SR Details***
Thank for your reply Sandeep.
Apart from Context.xml file, where the JDBC url is referred. Do we need to change anywhere else for referring the new schema?
Also have you tried this before, are there any risks/concerns involved?
Regards,
Sathiya
Referring in the Context.xml file should be fine. In the database rule type in the "How to connect" option, we can refer the database details using JDBC URL as well.
As risks/concerns are considered, just ensure the size and performance aspects of the database server.
Thanks
Sandeep P V
Yes, this is feasible. If you considered the database server size and the processing speed. As all NON-PROD env's are in single database, I would recommend involve the DBA.
Coming to the Database rule type configuration for the respective PEGA environment. For example, you are configuring using the JDBC URL, need to configure something like below
jdbc:oracle:thin:@//DATABASE_SERVER_NAME:PORT_NUMBER/SCHEMA_NAME
Thanks
Sandeep P V