There is already an object named 'PK_Survey_Category'

History:

1. drop table Survey_Category
2. create table Survey_Category:

CREATE TABLE [dbo].[Survey_Category] (
[Survey_Category_ID] [int] NOT NULL ,
[Survey_ID] [int] NOT NULL ,
[Survey_Category_Type_ID] [int] NOT NULL ,
[Title] [varchar] (128) NOT NULL ,
[Intro] [varchar] (255) ,
[Sequence] [int] NOT NULL ,
[F_Title] [varchar] (128) ,
[F_Intro] [varchar] (255)
) ON [PRIMARY]

3. Run:
alter table Survey_Category add constraint PK_Survey_Category primary key(Survey_Category_ID) with fillfactor=90

ERROR:
There is already an object named 'PK_Survey_Category' in the database

4. alter table Survey_Category drop constraint PK_Survey_Category

5. ERROR:Constraint 'PK_Survey_Category' does not belong to table 'Survey_Category'

-----------------

QUESTION: When I dropped a table didn't it
drop all the constraints automatically?
And if PK_Survey_Category still exists why it doesn't allow me to drop it?

The error indicates that there is some other table with a constraint using that name.



Constraint names must be unique within a schema.

Thank you very much, swampBoogie!

I just found it out myself
that i have to use information_schema.table_constraints
2 minutes ago.

Anyway, thank you for trying to help.

RobO