Database properties - severe issue

[eric lawson]

I seem to be one of a very large number of analysts who have a VISIO database diagram, loaded with database properties, such as keys, descriptions, triggers etc. but with no identified method for extracting these, via reporting or "database schema generation (forward engineering)".

Apparently, the foward engineering function is in the Enterprise Edition. This does frustrate me as the informative flash demos on the microsoft site suggest otherwise, particularly for SQL Server etc.

However, the mimimum I would expect of a Professional version (I use 2003), would be the ability to generate reports on these attributes, particularly as they certainly seem to be stored in an internal database.

SO GIVEN THE AMOUNT OF POSTS (search on "database" or "database print" or "database properties") I THINK IT APPROPRIATE THAT SOMEONE FROM MICROSOFT RESPOND URGENTLY WITH A SOLUTION.

As a database analyst, I do not want to create a VB programming task for someone else in the department. The inability to extract the database properties information somewhat defeats the functional purpose of the VISIO model (however, it is great for publishing information).

 

[eric lawson]

Thanks for your response Coyote! Do you know of any way to get MS to respond to this. They do appear to answer some queries, quite well at times

Overall the product is great, and wih some enhancements to the reporting features it could be excellent. I am happy to do basic coding to convert attributes to DDL, but I dont want to have to delve into VISIO internals to get the attributes out first.

 

[Lori Pearce \(MSFT\)]

Best way to get the proper attention is to post in the most specific
newsgroup. Try posting questions about database functionality in
Microsoft.public.visio.database.modeling.

--
Lori Pearce
Longhorn SDK

Thanks for your response Coyote! Do you know of any way to get MS to

respond to this. They do appear to answer some queries, quite well at times.

Overall the product is great, and wih some enhancements to the reporting

features it could be excellent. I am happy to do basic coding to convert
attributes to DDL, but I dont want to have to delve into VISIO internals to
get the attributes out first.