Microsoft KB Archive/914780

= Error message when you try to use a merge publication that you created in SQL Server 2005: &quot;Precomputed partitions cannot be used&quot; =

Article ID: 914780

Article Last Modified on 4/18/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Developer Edition

-



BUG #: 408626 (SQLBUDT)



SYMPTOMS
When you try to use a merge publication that you created in Microsoft SQL Server 2005, you may receive one of the following error messages:

Error message 1

Precomputed partitions cannot be used because articles &quot;%s&quot; and &quot;%s&quot; are part of a join filter and at least one of them has a constraint with a CASCADE action defined.

Error message 2

The logical record relationship between articles &quot;%s&quot; and &quot;%s&quot; cannot be added because at least one of the articles has a constraint with a CASCADE action defined.

This problem occurs when the following conditions are true:
 * The Precompute partitions setting of the merge publication is set to True.
 * The merge publication contains an article that is based on a table that is specified to use cascading referential integrity constraints.
 * The merge publication contains join filters for the article.



CAUSE
This problem occurs because precomputed partitions cannot be used for a table that is specified to use cascading referential integrity constraints.



Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005



WORKAROUND
To work around this problem, set the Precompute partitions setting to False. Alternatively, rewrite the referential integrity constraints by not using cascading referential integrity.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1.

