S
Scott Abelmann
I posted this in the modeling group a few weeks ago and didn't get any
hits...
Hopefully I will have better luck here...
I am experiencing a couple issues with Visio for Ent. Arch when using the
database modeling functionality. The first one has to do with some strange
behavior when I attempt to refresh my database model from my SQL2000
database. When I create a new stored procedure outside of Visio and then
attempt to refresh my model to pick up the new proc, Visio fails to detect
any changes in the database and the proc is not imported. However, if I
create a brand new database diagram and do a new reverse engineer, the
stored proc is imported into the model as expected. I can further verify
this when looking at the import/export log generated by the refresh -- the
new stored procedure is not listed there nor is it counted in the summary
information at the end (indicating the total number of procs examined).
The second issue has to do with updating the database with changes to stored
procs made through Visio's code editor. When I update an existing proc
through the code editor and attempt to push the changes to SQL2000, it bombs
with a bunch of errors and the updates are not made. Upon further
examination, it appears that the drop statements issued before the procs are
recreated are not properly quoted. There is an opening double quote in
front of the proc name, but the trailing quote is omitted rendering the SQL
invalid and causing the update to fail.
My environment is as follows:
Client - WinXP Pro SP1 and Visio for Ent Arch. (10.0.2705) <<
installed with VS.NET 2003
Server - Win2000 Server SP4 and SQL 2000 Dev Edition SP3 (8.00.818)
If anyone has any experience with either of these issues, workarounds,
and/or fixes I would greatly appreciate any input.
Thanks in advance,
-Scott
hits...
Hopefully I will have better luck here...
I am experiencing a couple issues with Visio for Ent. Arch when using the
database modeling functionality. The first one has to do with some strange
behavior when I attempt to refresh my database model from my SQL2000
database. When I create a new stored procedure outside of Visio and then
attempt to refresh my model to pick up the new proc, Visio fails to detect
any changes in the database and the proc is not imported. However, if I
create a brand new database diagram and do a new reverse engineer, the
stored proc is imported into the model as expected. I can further verify
this when looking at the import/export log generated by the refresh -- the
new stored procedure is not listed there nor is it counted in the summary
information at the end (indicating the total number of procs examined).
The second issue has to do with updating the database with changes to stored
procs made through Visio's code editor. When I update an existing proc
through the code editor and attempt to push the changes to SQL2000, it bombs
with a bunch of errors and the updates are not made. Upon further
examination, it appears that the drop statements issued before the procs are
recreated are not properly quoted. There is an opening double quote in
front of the proc name, but the trailing quote is omitted rendering the SQL
invalid and causing the update to fail.
My environment is as follows:
Client - WinXP Pro SP1 and Visio for Ent Arch. (10.0.2705) <<
installed with VS.NET 2003
Server - Win2000 Server SP4 and SQL 2000 Dev Edition SP3 (8.00.818)
If anyone has any experience with either of these issues, workarounds,
and/or fixes I would greatly appreciate any input.
Thanks in advance,
-Scott