Duplicate records in Prospect table in SQL Server cause TIE nightly refresh to fail

 In TIE (The Information Edge), users discover that the nightly refresh failed during the creation of the Constituent table due to a Primary Key violation. It was found that one particular record's System ID was duplicated in the Prospect table, both holding that system ID as their foreign key. Users may also find that each Prospect ID had a corresponding set of Ratings in the Ratings table. However, only the ratings for one of the Prospect IDs are correct. From the front end of the RE database, everything looks correct, only showing the one Prospect system ID that shows the correct corresponding Ratings.

If you encounter this issue in the latest version and patch of Raiser's Edge please contact support and reference this article.

Environment

 7.91.5056, patch 9 ; Duplicated in 7.91.5056, patch 16

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.