Using : LLBLgen 3.5 final (17 march), SQLSErver 2008R2

Hello,

I just wanted to move a version of our app to another environment, but when I create the SQL script of our database using "Create Database schema Create Script (DDL SQL)" , the unqie constraints are not included. I'm sure this worked before, because when I look into our source control where we keep previous scripts, the unique indexes were included.

As a test, I created a brand new LLBLgen project, connected to the DB , added all tables and saved the llblgenproj file. If I look in the llblgenproj file and search for "IX_", I only find 2 unique indexes (while we have dozen's). It looks like this in the llblgen proj file :

              <UniqueConstraints>
                <UniqueConstraint Name="IX_ResultList">
                  <Field Name="Name" />
                </UniqueConstraint>
              </UniqueConstraints>
            </Table>

These 2 unique constraints are also the ones created in the DDL SDQL script. but all the others are gone ? If i look in the original database with SSMS, I see no difference why the unique index on those two tables are included in the LLBLGen project, and all the others are not ...

Please help ...

EDIT: my bad; It seems the previous scripts were generated with SSMS and not with LLBLGen. Furthermore, the two uniques that are included in LLBLGen are really unique KEY while all others are unique INDEX (and for some reason, LLBLgen skips this, but the SSMS script generation does not ..)

releases on saturdays are always fun ...

If you refresh the catalog from your DB and then export the Create DDL, Does it work? AFAIK, LLBLGen doesn't manage indexes.

Should we consider this closed? or Do you have additional questions/inquires?