Question
Owens & Minor
US
Last activity: 19 Mar 2018 11:30 EDT
Database colocation SQL instance
Currently we are using SQL 2014 in an HA configuration for hosting PRPC 7_3 database. We deployed a persistence cluster running SQL 2014 HA to host additional application related data. There are issues with distributed transactions between these two linked servers. Is there any issues with colocation of these persistence databases with the PRPC 7_3 database on the same SQL instance? We want to ensure we are running in accordance with PEGA beat practices and not creating an issue that could adversely effect the availability of PRPC.
***Updated by moderator: Lochan to update Categories***
Accepted Solution
Owens & Minor
US
After conversations with our Pega Practice Leader and product SME's it was determined that PRPC database isolation was not a requirement for support. My experience with other application suites was that seeding other databases would void support requests. This was thankfully not the case as we have a database query that could not execute as a distributed query from another SQL instance (both servers were running SQL 2014). We will still need to monitor SQL instance performance closely to ensure there are no resource bottle necks or locks/blocks/waits that impact application availability.
Pegasystems Inc.
IN
From the SR notes I noticed that your team has had discussions within Pega, outside of the SR. Please let us know the update and if you are still needed help from our community.
Regards,
Accepted Solution
Owens & Minor
US
After conversations with our Pega Practice Leader and product SME's it was determined that PRPC database isolation was not a requirement for support. My experience with other application suites was that seeding other databases would void support requests. This was thankfully not the case as we have a database query that could not execute as a distributed query from another SQL instance (both servers were running SQL 2014). We will still need to monitor SQL instance performance closely to ensure there are no resource bottle necks or locks/blocks/waits that impact application availability.