OK, I know the reason now.
For a schema (generated by DdlUtils from a live database) as following:
DdlUtils generates sql statements :
CREATE TABLE "Accrual"
"AccrualID" NUMERIC(8,0) NOT NULL IDENTITY (1,1) ,
"PeriodFK" NUMERIC(8,0) NOT NULL,
"FileNameChanged" VARCHAR(80) NOT NULL,
PRIMARY KEY ("AccrualID")
CREATE UNIQUE INDEX "PK_Accrual" ON "Accrual" ("AccrualID")
CREATE INDEX "IX_Accrual_Period" ON "Accrual" ("PeriodFK")
OK. It looks all right so far.
But on SQL Server 2000, with the PRIMARY KEY ("AccrualID")
in the create table statement, an index called PK__Accrual__XXXXXX will
generated automatically on the table, here is where the extra index come
However, if I don't include primary key in the create table statement but
alter table Accrual
add constraint PK_Accrual primary key
later to define primary key, the index is called PK_Accrual which is what it
I'm not sure is this something that I can config on the SQL Server or
DdlUtils should take care of this.