31. ledna 2008 17:22I'm running Visio 2007 SP1 against SQL Server 2005 SP2. I used the reverse engineer function to bring all the tables into Visio. I made changes in the database through SQL Server and ran the refresh model option to bring the chnages into my visio diagram. Visio found changes to several tables I did not touch and well as all the ones I did change. The lookup tables it listed as changed all have a unique index on a single column. After the refresh each of these columns had another unique index listed. I have tried re-starting Visio 2007 to re-run the refresh and now have 3 unique indexes listed. How can I avoid this?
26. listopadu 2008 20:52I'm having the same problem.
31. července 2009 20:25
I, too, am having the same problem, although I am running against SQL Server 2000 (I've seen this behavior with SQL 2005, though). For any table with a non-PK unique index (i.e., on a Name field), Visio, upon refreshing the model, generates multiple copies of the same index (i.e., U1, U2, etc. - all with the same Index Name under the Database Properties->Indexes tab). I am getting quite tired of having to manually delete all of these bogus duplicate indexes every time I do a database refresh (which can happen many times per day).
Would someone from the Visio team (or anyone who knows how to prevent this behavior) please respond to this thread?
16. dubna 2010 18:25Same here, and it's very frustrating!
4. srpna 2010 14:42Same problem here with Visio 2007 and Sql Server 2008. Any workaround? Solution?
27. srpna 2010 17:05
There are some workaround solution as following (Source from website):
Manually seek out the tables with unique indexes and remove each duplicate in turn. And make sure you don't run refresh Model on these tables.
Hope it can help you.
Peace Through Tyranny
6. října 2010 15:52I am experiencing the same problem with Visio 2010 and PostgreSQL. Very frustrating, because the schema I am working with is too large for manual removal and re-addition to be a practical workaround.
18. října 2010 22:12
Wow.. first reported Jan 2008 and its *still* a problem? I guess Microsoft doesn't want us to use or recommend this tool.. This should NOT be an issue! I can't believe this passed their tests....
1. dubna 2011 14:29
Alas, if this is still an issue with Visio 2010, then there's NO WAY we can justify our upgrading from 2007, even though 2007 doesn't support reverse engineering from SQL 2008 without Generic OLE DB datatype-less jiggery-pokery workarounds (obviously a business decision, rather than a technical one) - especially considering that there's no upgrade path from 2007, just full $$.
I don't know if this is evidence of MS's withdrawing support from Visio as a DB tool (perhaps hoping we'll just use SSMS's painfully slow, borderline unreadable, one-wrong-click-and-you're-screwed diagramming tool), or simply of MS's disdain for those of us toiling with their tools without enterprise-grade support contracts, but the message is clear: Find a different DB diagramming tool (ERWin, TOAD, RedGate, Altova, DeZign for DB, etc.).
10. dubna 2012 17:43As of 4/10/2012, Visio Premium 2010, Version 14.0.6112.5000 (32-bit) still have the same problem (working with Microsoft SQL server 2008).
15. června 2012 20:45
I have been refreshing from Visio Professional 2010 on a Sql2005 database and it has been working fine until now, but now I am seeing this bug. Three things just changed.
1) We had been making the database schema changes in Management Studio and this time we deployed the database schema from a Visual Studio database project.
2) The tables are now using calculated fields like ALTER TABLE [dbo].[ThisTable] ADD [OtherTableCount] AS ([dbo].[ThisTableOtherTableCount]([ThisTableID])) where ThisTableOtherTableCount is a scalar-value function.
3) I had been using the Generic OLE DB Provider, but then I used the Microsoft SQL Server driver. I now get this behaviour using either driver.
Could those changes have anything to do with bringing out this buggy behaviour?
- Upravený dfdsdfdasfas 15. června 2012 20:56