Database Clash Occurs After an Upgrade

Problem: A database clash occurs following an upgrade

Description: A database clash occurs if you backup and restore a Server database onto the same SQL Server instance under another name.

Cause: The P2 Server database will keep the original GUID used to identify the Data Broker and clash with the original source database.

Resolution: To resolve this, run the following command on the database following the upgrade:

ALTER DATABASE cadrondemo01_Server40 SET NEW_BROKER

Comments are closed