FIX: Error Message 8630 Occurs When Updates are Performed to a Table with Compound Keys

A table with compound keys, which has a Primary key constraint with a nonclustered index and foreign key constraints, returns an 8630 error message during an update:

To work around the problem you can change any one of these items on the table definition:

• Make the index for the Primary key clustered instead of nonclustered.
  
  
• Create a surrogate Primary key on the table or pick another candidate key as your Primary key on the table.
  
  
• Drop the foreign key constraint on the table.

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information, contact your primary support provider.

The table must have all of the constraints that follow defined to demonstrate the problem: The update will not fail with the 8630 error if:

• The key is not a compound key.
  
  -or-
  
  
• The foreign key or Primary key constraints are missing.
  
  -or-
  
  
• The Primary key index is clustered.