Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sathiyamoorthy Subramanian (SathiyamoorthyS4456)
Services Australia
Pega Architect
Services Australia
AU
SathiyamoorthyS4456 Member since 2016 1 post
Services Australia
Posted: Apr 22, 2018
Last activity: Apr 26, 2018
Posted: 22 Apr 2018 19:52 EDT
Last activity: 26 Apr 2018 15:20 EDT
Closed

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***

To see attachments, please log in.
Data Integration
Support Case Exists

Posted: 6 years ago
Posted: 23 Apr 2018 3:00 EDT
Venkata Sandeep Kumar Pamidamarri (SandeepPamidamarri)
Toyota Financial Services
Venkata Sandeep Kumar Pamidamarri
Toyota Financial Services
AU

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

To see attachments, please log in.
  • Akanksha Khan Vitaliy Orfenov Aushadh Bhasha Syed Sravan Kumar Papani SHAIK ROSHAN ALI BABA and 4 More
Posted: 6 years ago
Posted: 24 Apr 2018 0:23 EDT
Sathiyamoorthy Subramanian (SathiyamoorthyS4456)
Services Australia
Pega Architect
Services Australia
AU

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

To see attachments, please log in.
Posted: 6 years ago
Posted: 24 Apr 2018 1:31 EDT
Venkata Sandeep Kumar Pamidamarri (SandeepPamidamarri)
Toyota Financial Services
Venkata Sandeep Kumar Pamidamarri
Toyota Financial Services
AU

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

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice