J
Janez
Hi,
I have a problem with unique index when reverse engineering SQL Server
2000 database. Here are the steps to reproduce this behavior:
1. Create new database with Enterprise Manager and add one table to
this database with two fields:
ID - smallint, not null, primary key
Title - nvarchar(50),not null
2. Create new unique index for the field Title in Enterprise manager.
3. Create ODBC datasource for the database.
4. Start Visio 2003 and reverse engineer the database. Everything is
added to the Database model diagram as expected.
5. Refresh database model with 'Refresh model' menu option in Visio
without changing anything in the database structure. Refresh wizard
reports changes to the unique index on Title field and if you choose
to refresh database new unique index is added to the model. If you
choose 'Refresh model' again wizard again reports the same change and
so on ..
The problem does not occur with non-unique index.
I am using Visio 2003 with SP1 (11.4301.6360).
Any help?
Regards
Janez
I have a problem with unique index when reverse engineering SQL Server
2000 database. Here are the steps to reproduce this behavior:
1. Create new database with Enterprise Manager and add one table to
this database with two fields:
ID - smallint, not null, primary key
Title - nvarchar(50),not null
2. Create new unique index for the field Title in Enterprise manager.
3. Create ODBC datasource for the database.
4. Start Visio 2003 and reverse engineer the database. Everything is
added to the Database model diagram as expected.
5. Refresh database model with 'Refresh model' menu option in Visio
without changing anything in the database structure. Refresh wizard
reports changes to the unique index on Title field and if you choose
to refresh database new unique index is added to the model. If you
choose 'Refresh model' again wizard again reports the same change and
so on ..
The problem does not occur with non-unique index.
I am using Visio 2003 with SP1 (11.4301.6360).
Any help?
Regards
Janez