SQL Server 2008 Driver for Visio 2007 - by v-dionei

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 365757 Comments
Status Closed Workarounds
Type Bug Repros 25
Opened 9/2/2008 12:36:08 PM
Access Restriction Public


I used to be able to reverse engineer tables and views from a Microsoft SQL Server 2005 database using Visio 2007.  The database has been migrated to SQL Server 2008 and I can no longer reverse engineer tables and views using Visio 2007.  
Sign in to post a comment.
Posted by MaximeFortier on 9/26/2012 at 8:40 AM
What's the status with Visio 2010 aiming at SQL Server 2012?
Posted by Pedro M. Sousa on 5/19/2011 at 4:21 AM
"Further investigation reveals that this is expected behavior for Visio 2007." This sucks!!!
Posted by Cellfish Media on 7/20/2010 at 10:14 AM
This really sucks. Microsoft clearly does not support it's own products. I don't think it would be such a big deal for Microsoft to update it's Visio driver in order to support SQL-2008 and its new datatypes. Generic ODBC driver is not a proper solution as it messes up the datatypes, which makes the model useless.

Microsoft should indicate in their SQL-2008 white paper "Our own products are not compatible with each other. Therefore our databe modeling tool does not support our own database product. Please consider using competitors' database and modeling products for a complete integrated solution. We do not consider database modeling and proper planning to be a best practice."

Although Visio for Enterprise Architects was available in my MSDN PRO subscription downloads, and provided somewhat proper tools for SQL-2005, Visio 2010 is not available for download. If it's true that Visio 2010 does work for reverse engeneering SQL-2008 databases (which I can't tell), will it work for generating DDL scripts out of my model? Will it properly support schemas and new datatypes? I shouldn't have to purchase an Office 2010 license only to find out it doesn't.

Microsoft should provide proper updates to Visio and make them available for download either through Microsoft Updates or MSDN PRO (and higher) subscription downloads.
Posted by SuckeeSuckee5Dollar on 5/28/2010 at 9:29 PM
You guys are SOBs.
Posted by rahul_jha1 on 5/11/2010 at 5:30 AM
Can this ticket be reopened? If MS is not ready to provide the solution, then we have to shift to RR and say bye to VISIO for ever...
Posted by Keith_EN on 2/22/2010 at 1:52 PM
So is there any support for "Engineering" or "Updating" Sql Server 2008 in any Visio product?
Or does Microsoft not support Sql Server 2008?
Posted by MTB09 on 11/29/2009 at 5:35 PM
I've been using Visio for Enterprise Architects for creating models and uploading (forward engineering) to SQL Server 2005. We are in a new development phase and Visio Works great. But the inability to migrate to a version of Visio that can interface with SQL Server 2008 PREVENTS us from moving to SQL Server 2008!!!

Guys at MS - Don't you get this? You cannot sell 2008 without providing your customers with migration paths for the supporting tools. Is there a technical issue here that we are all missing that prevents this from being fixed?

Can someone at MS address this issue - at least give a time table for a solution.

BTW - I tried the workarounds but there are way too many issues with datatypes to be of real use.
Posted by TimeBytes on 11/9/2009 at 8:58 AM
Wow. Someone forgot to set a flag, and they claim this is by design.

Nice try, MS.

All of the work-arounds that I've tried, mess up the column datatypes. Makes the diagram close to (but not completely) useless.

ODBC is specifically designed so you can fall back to a simple set of behavior that works across versions. There is no technical reason whatsoever why SQL Server 2008 and Visio 2007 could not communicate simple stuff like table names and datatypes using the same ODBC that worked with SQL Server 2005.
Posted by Jonathan Manley on 10/20/2009 at 12:28 PM
This needs to be fixed, the ODBC Driver does not work well with the new data types (fileStream) and the workaround is not acceptable.
Posted by MrEdba on 7/23/2009 at 10:43 AM
This ticket needs to be reopened. Closing it as "By Design" is VERY poor customer service.
Posted by Ty Parten on 7/23/2009 at 7:26 AM
This is completely unacceptable. Microsoft is really letting us all down with this kind of response/attitude.
Posted by phuff34 on 4/28/2009 at 11:02 AM
Wow. Typical. I'm growing tired of this arrogant behavior from MS.

Get Rational Rose and forget this. I've been a software engineer for 5 years, almost entirely in .Net, and can tell you I'm looking at making a move from the MS world. Burned by too many things. I'll either move to Java development (and not on Windows) or stick with Mac development with Objective-C. Mac and iPhone development is fun.
Posted by KindergartenCoder on 4/28/2009 at 9:54 AM
Stingray3's recommendation is the best solution I've been able to find. A few other comments: when you run the Reverse Engineer Wizard in Visio 2007 select the ODBC Generic driver from the "Installed Visio drivers" drop-down. Then create a new data source using the SQL Native Client (2005.90.4035, 2005 SP3). You'll get a warning stating that some information retrieved may be incomplete. Click OK and continue. It's not the most intuitive solution, but at least this will allow you to use your existing version of Visio to connect to SQL 2008.
Posted by Hong861482 on 4/21/2009 at 8:22 AM
Vissio 2007 does not play well with SQL Server 2008 and MS suggest you to buy a future version of Visio just for you to get it to work with SQL Server 2008. Why not try some other tools, like Enterprise Architect.
Posted by mityak on 3/13/2009 at 1:23 PM
First MS drop forward engineering in VISIO 2007 and now this. Please fix it. And please put forward engineering back.
Posted by shaannannan on 2/10/2009 at 11:54 AM
http://stackoverflow.com/questions/92811/reverse-engineering-for-database-diagramming-in-visio-with-sql-server-2008 might help you going.
Posted by tonysell on 1/16/2009 at 12:49 PM
Closed by design and not a blocking issue - Nice try. This truely is a bug and should be fixed and an update posted. I do a great deal of reverse and forward engineering of databases (forced to use Visio EA 2003 since there have been no updates there either). Visio 2003 even supports SQL 2005 so the response to this issue is truely not acceptable.
Posted by Stingray31 on 12/18/2008 at 6:16 PM
This can be fixed by using the Generic ODBC driver and defining a User DSN on your machine. This also works best for using Visio 2007 with Oracle 10g Servers as well. This is how I am currently connecting and it work just fine, however it would be nice if Microsoft supported the SQL Native client.

Posted by byersjus on 11/25/2008 at 8:52 AM
I can't understand how they (MS) could drop the ball this badly. I love to model with Visio and now their inexpensive Office application's limitations are stopping our transition to SQL 2008, what they really want to sell.
Posted by Edofin on 10/31/2008 at 12:03 PM
Okay, Great. Gotta love it when the 'current' tools don't work and Microsoft just says you (not MS) can fix it 'later 'by 'buying into' what we come up with next.
Posted by Microsoft on 9/10/2008 at 2:21 PM
Further investigation reveals that this is expected behavior for Visio 2007. When Visio opens a connection using the Visio SQL Server Driver it checks the server version and since SQL Server 2008 shipped after Visio 2007 it doesn't recognise SQL Server 2008 as a supported version and closes the connection. You can wait for a future version of Visio to ship which does recognise SQL Server 2008 or use the Visio Generic ODBC driver which can successfully open connections to SQL Server 2008. A third option is to use a copy of SQL Server 2005 for initial reverse engineering. The Visio team is aware of this issue.

Thank you for reporting this issue.
Posted by Microsoft on 9/5/2008 at 11:21 AM
Thank you for your feedback. We have started investigating your problem.