Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Join is not working across database instances

SA-37324

Summary



A report runs on a class that points to the rules database and has a join with a class that points to the work/data database.

When the report runs, the sub report queries the rules database instead of the work.


Error Messages



Error: ** An error occured on executing the query for the report definition - There was a problem getting a list: code: 208 SQLState: S0002 Message: Invalid object name 'PEGA_DATA.vw_XXX_WorkList'. DatabaseException caused by prior exception: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'PEGA_DATA.vw_XXX_WorkList'. | SQL Code: 208 | SQL State: S0002


Steps to Reproduce

  1. Create rules and work/data databases in two separate instances.
  2. Create a report definition in a class which is in Rules database.
  3. Join with a class which is in work/data database.
  4. Run the report.

Root Cause



Pega 7 supports split schema within one database but has not totally eliminated queries that join rules to data.

Thus, Pega 7 does not support configuring rules and data in two totally separate databases instances.

Resolution



Usage of spilt schema is preferred in this situation.

Published June 1, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us