G
Gshell
I just upgraded my instance of Visio for Enterprise Architects from 2003 to
2005. I took an old VISIO model of my database and opened it in VEA 2005.
I made a backup copy of my SQL server database and was going to test a round
trip from the database to VEA2005 and back, just to be certain things worked
well. I clicked on the "Database" menu and then selected "Update" and got an
error dialog indicating that the model did not validate and I needed to fix
some errors first. I opened the output window and saw a series of error
messages all like this one. "D:\My Documents \my_Modeler.vsd : error P1033:
'"MasterIdentity"' : Constraint name is not unique. The target DBMS requires
the constraint name to be unique in the database."
The underlying database is SQL Server 2000. And clearly the "error" above
is incorrect. The target DBMS does does not require that the contstarint
name to be unique. I double clicked the error to see which table it
referenced and then drilled down into the properties of the table. The
MasterIdentity refers to a non-unique index in the table. I have several
tables that all have an identically named index. SQL 2000 does not complain
about this. The old version of VEA (2003) did not complain about this.
I verified that the menu "Database\options\drivers" settings were for SQL
2000, thinking that maybe they had defaulted to SQL2005 and that it migh have
such a rule. But the settings are for SQL2000. ANyone know why I am getting
this and short of renaming the indexes, how I might coax VEA2005 into being a
tad more "friendly"???
Thanks,
Gary
2005. I took an old VISIO model of my database and opened it in VEA 2005.
I made a backup copy of my SQL server database and was going to test a round
trip from the database to VEA2005 and back, just to be certain things worked
well. I clicked on the "Database" menu and then selected "Update" and got an
error dialog indicating that the model did not validate and I needed to fix
some errors first. I opened the output window and saw a series of error
messages all like this one. "D:\My Documents \my_Modeler.vsd : error P1033:
'"MasterIdentity"' : Constraint name is not unique. The target DBMS requires
the constraint name to be unique in the database."
The underlying database is SQL Server 2000. And clearly the "error" above
is incorrect. The target DBMS does does not require that the contstarint
name to be unique. I double clicked the error to see which table it
referenced and then drilled down into the properties of the table. The
MasterIdentity refers to a non-unique index in the table. I have several
tables that all have an identically named index. SQL 2000 does not complain
about this. The old version of VEA (2003) did not complain about this.
I verified that the menu "Database\options\drivers" settings were for SQL
2000, thinking that maybe they had defaulted to SQL2005 and that it migh have
such a rule. But the settings are for SQL2000. ANyone know why I am getting
this and short of renaming the indexes, how I might coax VEA2005 into being a
tad more "friendly"???
Thanks,
Gary