question

65206286 avatar image
0 Votes"
65206286 asked 65206286 commented

Data Quality Services Error "Failed to Execute Parallel Process" resolution

I tired the steps as instructed in this question to fix this problem but it did not work.
https://docs.microsoft.com/en-us/answers/questions/229512/has-anyone-solved-the-data-quality-services-error.html

I tried to drop and create the B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK Key adding the on delete cascade using the code below.
The key was altered.
But when I try to create a matching Policy I still get the error and when I go back and look at the key its reverted back to its original state without the cascade delete.

How can I fix this?

USE [DQS_PROJECTS]
GO

ALTER TABLE [KnowledgeManagement1000001].[B_INDEX_LEXICON_EXTENSION] DROP CONSTRAINT [B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK]
GO

ALTER TABLE [KnowledgeManagement1000001].[B_INDEX_LEXICON_EXTENSION] WITH NOCHECK ADD CONSTRAINT [B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK] FOREIGN KEY([TERM_ID]) REFERENCES [KnowledgeManagement1000001].[B_INDEX_LEXICON] ([ID]) On Delete Cascade
GO

ALTER TABLE [KnowledgeManagement1000001].[B_INDEX_LEXICON_EXTENSION] CHECK CONSTRAINT [B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK] GO

sql-server-general
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
You can display more detailed error messages like the thread you quoted. Or did you get the exact same error message as it?

0 Votes 0 ·

I get the same error message.

here is the snipit of the log file again.

Microsoft.Ssdqs.Core.Service.Calibration.CalibrationException: Execution of parallel task failed. ---> System.Data.SqlClient.SqlException: The DELETE statement conflicted with the REFERENCE constraint "B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK". The conflict occurred in database "DQS_PROJECTS", table "KnowledgeManagement1000001.B_INDEX_LEXICON_EXTENSION", column 'TERM_ID'.;
The statement has been terminated.;

0 Votes 0 ·

1 Answer

Criszhan-msft avatar image
0 Votes"
Criszhan-msft answered 65206286 commented

Hi,

The DELETE statement conflicted with the REFERENCE constraint "". The conflict occurred in database " ", table "", column "";

This error means that the data you want to delete is referenced by another table (foreign key). Creating foreign key constraints with the on delete cascade should be a solution.

when I go back and look at the key its reverted back to its original state without the cascade delete.

Do you mean that you modified fk constraint on the table to add the on delete cascade, but this operation seems to be rolled back?

Please apply the latest cumulative update to the SQL Server instance to avoid any possible issue.

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I am trying to create a matching Policy in DQS. When I do I get and error message. see image. the logs show

System.Data.SqlClient.SqlException: The DELETE statement conflicted with the REFERENCE constraint "B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK". The conflict occurred in database "DQS_PROJECTS", table "KnowledgeManagement1000001.B_INDEX_LEXICON_EXTENSION", column 'TERM_ID'.;
The statement has been terminated.;

continued in second message.




0 Votes 0 ·

Second message

In another thread I saw an instruction to alter the foreign key. I did that using this SQL. my changes have double quotes around them.

USE [DQS_PROJECTS]
GO

ALTER TABLE [KnowledgeManagement1000001].[B_INDEX_LEXICON_EXTENSION] DROP CONSTRAINT [B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK]
GO

ALTER TABLE [KnowledgeManagement1000001].[B_INDEX_LEXICON_EXTENSION] "WITH NOCHECK" ADD CONSTRAINT [B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK] FOREIGN KEY([TERM_ID]) REFERENCES [KnowledgeManagement1000001].[B_INDEX_LEXICON] ([ID]) "On Delete Cascade"
GO

ALTER TABLE [KnowledgeManagement1000001].[B_INDEX_LEXICON_EXTENSION] CHECK CONSTRAINT [B_INDEX_LEXICON_EXTENSION_B_INDEX_LEXICON_FK] GO

Ran the matching policy again, error message. logs have same error. the foreign key is reverted back to what is was before I made my change.

78342-dqs-error.jpg


0 Votes 0 ·
dqs-error.jpg (78.7 KiB)

Hi,

the foreign key is reverted back to what is was before I made my change.

So you checked this foreign key constraint in the [DQS_PROJECTS] database and found that there were no changes in the end even if you ran the above ALTER statements.

As I am not familiar with DQS, I can't find a specific reason yet. I will continue to pay attention to this issue.
Or you can @ the asker and consult the solution in another thread you mentioned.

Also please apply the latest cumulative update to the SQL Server instance to avoid any possible issue.

0 Votes 0 ·

the Alter statement did work and the constraint was updated, but it reverts back to the original state when I run the Matching Policy again.

I will apply the cumulative update.

If the cumulative update does not resolve the issue where do I go to get support and get this fixed?

0 Votes 0 ·