Article ID: 239475
Article Last Modified on 7/19/2006
APPLIES TO
- Microsoft SQL Server 7.0 Standard Edition
This article was previously published under Q239475
BUG #: 56102 (SQLBUG_70)
SYMPTOMS
In certain circumstances, when you perform the following steps in the exact order listed, a handled access violation (AV) may occur:
- The existing primary key constraint is dropped from a table.
- An attempt is made to add a new primary key constraint to that same table.
- The attempt to add the new primary key constraint fails with the following error because of the existence of duplicates in the column (or columns) on which the key is being added:
- An attempt is made to run the sp_execute function against that table to delete a row or rows from the table.
WORKAROUND
Before adding the new primary key constraint, make sure that there are not any duplicate or null values in the column (or columns) on which the key is being added.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack SP2 for Microsoft SQL Server 7.0. For information about how to download and install the latest SQL Server Service Pack, see the following Microsoft Web site:
For more information, contact your primary support provider.
Additional query words: Msg 1505; 1750; Error 1750
Keywords: kbbug kbfix KB239475
