Is it possible to store application specific data(case data, history etc) in a separate database altogether, not as a separate schema with in same database? We have a scenario where we have PegaRules and PegaDATA schema in one data base server and application specific data(case, histroy and custom look up data) are in a separate database server. Will this work if we create a new datasource pointing to application specific DB and update all the corresponding data-admin-db-table mappings?
Are you moving the pegaDATA schema to the application specific data base. Ideally if you have RULES and DATA schemas in the different db should work. It might get complicated if the db servers are different
Posted: 6 years ago
Posted: 5 Apr 2017 14:31 EDT
Prasanth Nair (PNAIRSCT)
I don't think moving the work tables to another DB is a good option here, instead you can copy the work table instances from PegaData schema and save it in another table that belongs to external DB. You could try this by mapping the table of external DB to a class and with use of an activity you can copy the data instances of actual work table to the table of external DB. However the challenge would be if your most of the properties are in BLOB you may face a tough time having them extracted and exposing them in the tables.