I'm using v3405 and trying to install two forums using different table prefixes setup in config.asp
While installing the second forum I get an error that a contraint cannot be added because the "contraint SNITZ_373" already exists in the database.
I did a response.write of all the sql in setup.asp and found the offending statement -
CREATE TABLE SNITZ2_ALLOWED_MEMBERS (MEMBER_ID INT NOT NULL, FORUM_ID INT NOT NULL, CONSTRAINT SNITZ2_SnitzC373 PRIMARY KEY NONCLUSTERED (MEMBER_ID, FORUM_ID) )
The only other reference to a constraint with the same (almost) name is this sql statement
CREATE TABLE SNITZ2_MEMBERS ( MEMBER_ID int IDENTITY (1, 1) NOT NULL , M_STATUS smallint NULL , M_NAME nvarchar (75) NULL
DEFAULT '' , M_USERNAME nvarchar (150) NULL DEFAULT '' , M_PASSWORD nvarchar (65) NULL DEFAULT '' , M_EMAIL nvarchar (50) NULL
DEFAULT '' , M_COUNTRY nvarchar (50) NULL DEFAULT '' , M_HOMEPAGE nvarchar (255) NULL DEFAULT '' , M_SIG ntext NULL DEFAULT '' ,
M_VIEW_SIG smallint NULL DEFAULT 1 , M_SIG_DEFAULT smallint NULL DEFAULT 1 , M_DEFAULT_VIEW int NULL , M_LEVEL smallint NULL ,
M_AIM nvarchar (150) NULL DEFAULT '' , M_ICQ nvarchar (150) NULL DEFAULT '' , M_MSN nvarchar (150) NULL DEFAULT '' , M_YAHOO
nvarchar (150) NULL DEFAULT '' , M_POSTS int NULL DEFAULT '0' , M_DATE nvarchar (14) NULL , M_LASTHEREDATE nvarchar (14) NULL
DEFAULT '' , M_LASTPOSTDATE nvarchar (14) NULL DEFAULT '' , M_TITLE nvarchar (50) NULL DEFAULT '' , M_SUBSCRIPTION smallint
NULL , M_HIDE_EMAIL smallint NULL , M_RECEIVE_EMAIL smallint NULL , M_LAST_IP nvarchar (15) NULL , M_IP nvarchar (15) NULL ,
M_FIRSTNAME nvarchar (100) NULL CONSTRAINT SNITZ2_SnitzC0369 DEFAULT '' ,M_LASTNAME nvarchar (100) NULL CONSTRAINT
SNITZ2_SnitzC0370 DEFAULT '' ,M_OCCUPATION nvarchar (255) NULL CONSTRAINT SNITZ2_SnitzC0371 DEFAULT '' ,M_SEX nvarchar (50) NULL
CONSTRAINT SNITZ2_SnitzC0372 DEFAULT '' , M_AGE nvarchar (10) NULL CONSTRAINT SNITZ2_SnitzC0373 DEFAULT '' ,
M_DOB nvarchar (8) NULL DEFAULT '' , M_HOBBIES ntext NULL DEFAULT '' , M_LNEWS ntext NULL DEFAULT '' , M_QUOTE ntext NULL
DEFAULT '' , M_BIO ntext NULL DEFAULT '' , M_MARSTATUS nvarchar (100) NULL CONSTRAINT SNITZ2_SnitzC0374 DEFAULT '' ,M_LINK1
nvarchar (255) NULL CONSTRAINT SNITZ2_SnitzC0375 DEFAULT '' ,M_LINK2 nvarchar (255) NULL CONSTRAINT SNITZ2_SnitzC0376
DEFAULT '' , M_CITY nvarchar (100) NULL CONSTRAINT SNITZ2_SnitzC0377 DEFAULT '' , M_STATE nvarchar (100) NULL CONSTRAINT
SNITZ2_SnitzC0379 DEFAULT '' , M_PHOTO_URL nvarchar (255) NULL CONSTRAINT SNITZ2_SnitzC0378 DEFAULT '' , M_KEY nvarchar (32)
NULL DEFAULT '' , M_NEWEMAIL nvarchar (50) NULL DEFAULT '' , M_PWKEY nvarchar (32) NULL DEFAULT '' , M_SHA256 smallint NULL
DEFAULT '1' )
Anyone have an idea what is going on here?
Can I safely rename one of the constraints? I presume it doesn't matter what its called as long as its created?