Visio 2003 SQL Server 2005 driver - reverse engineering

[Kevin H]

I am attempting to reverse engineer a SQL Server 2005 database using Visio
2003. I've tried the following, each with less than perfect results.

Option: SQL Server Driver
Result: Error - Not a compatible data source

Option: Generic ODBC Driver
Result: Reads table objects
- will not read Stored Procs or Views
- does not handle complex data types (nvarchar and guid are converted
to longvarbinary data type)

Option: OLEDB Driver - SQL Native
Result: Reads table objects, Stored Procs and Views
- GUIDs are handled
- nvarchar is identified, but as wchar
- bit comes as boolean
- datetime comes as timestamp
This last one is my biggest problem here. Timestamp is a legitimate data
type for SQL, and it means something VERY different from datetime. But it's
troublesome that several come across strangely.

I searched the site for an updated driver, but found none. Any suggestions?

 

[Al Edlund]

I just did a reverse engineer against SqlSrv2005 using v2005EA (which came
with VisStudio2005 Architect Edition) and it appears to have worked. I
haven't tried the DDL yet but datetime came out correctly identified in both
table and SPCs. As I remember prior to SqlSrv2005/VisStudio 2005 going
generally available the comments were that the necessary drivers would be in
VisStudio2005 (since the database addon is owned by development not visio).
Al

 

[Kevin H]

Unfortunately, I don't have Visual Studio available. Visio Architect Edition
is now "conveniently" only available with Visual Studio. And my
understanding is that the software you just described is in the "thousands of
dollars" price range.

Can I get an updated driver for my Visio Professional 2003 product? Or is
my only option to buy some very expensive software that I don't need?

 

[Rhys]

Reverse Engineering SQL 2005 DB from Visio

When you try to Reverse Engineer SQL 2005 DB from Visio 2003. You may
get this error “The currently selected Visio driver is not compatible
with the data source."

I think SQL Server 2005 compatible driver will be shiped later.

However, you may use Generic OLE DB Provider, and then select
Microsoft
OLE DB Provider for ODBC drivers, it can successfully interpret tables
with
from SQL Server 2005.