Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

How to access both SQL Server 2000 and SQL Server 2005 databases from one Process Commander system

Updated on September 13, 2021

Symptom

Process Commander can connect to any of several databases, including Microsoft SQL Server 2000 and SQL Server 2005. To implement the JDBC drivers for MS SQL Server, you need to enter the appropriate driver information in the prconfig.xml file.

The syntax for loading the 2005 JDBC driver is:

com.microsoft.sqlserver.jdbc.SQLServerDriver

The syntax for the 2000 driver is:

com.microsoft.jdbc.sqlserver.SQLServerDriver

When you load both drivers on the same process, your system may crash when you attempt to retrieve data from the database.

This system crash occurs because the 2000 version of the JDBC driver is incorrectly accepting the 2005 microsoft.sqlserver.jdbc prefix.

Solution

To resolve this issue, you need to load the 2005 version of the driver first. Enter the driver information in prconfig.xml as follows:

<env name="database/drivers" value=" com.microsoft.sqlserver.jdbc.SQLServerDriver; com.microsoft.jdbc.sqlserver.SQLServerDriver" />

This ensures that the 2005 driver handles the prefix microsoft.sqlserver.jdbc and the 2000 driver handles the prefix microsoft.jdbc.sqlserver.

 

 
  • Previous topic Managing Elasticsearch index host nodes outside of the Search landing page
  • Next topic How to configure non-J2EE database connections in the prconfig.xml file

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect System/Cloud Ops Administrator System Administration

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us