SQL 2005 and Visio for Enterprise Architects Database

I reverse engeneered a SQL2005 database into Visio for EA where I had utilized the new schema feature (like what was done in the sample Adventure Works database). After the db schema was generated I was happy to see the the schema name appeared in the owner attribute of the table definition. However, I was unable to change the owner to a different schema name. Additionally, if I create a new database design, it appears I cannot associate an owner (schema) to the table. Am I missing something If I name the table with a dot notation to include the schema name, it prepends the dbo owner as well.

Any recommendations I like the notion of using schemas for security purposes.

Thanks,

Tom




Answer this question

SQL 2005 and Visio for Enterprise Architects Database

  • Tasha O.

    I've checked with Visio EA team and I can confirm that you cannot do what you'd like to do with the current version of our products.

    We are evaluating whether this is a common need and if we would have to include this feature in future Visio releases.

    Regards

    Mauro Regio



  • João Pereira

    What kind of bullshit is this half of SQL2005 is supported in Visio, the other half is to be evaluated ! ! Are you saying you guys aren't sure if you should support the features of your own software

    And to Roger_Wolter_MS: if you ever installed VS2005, you'd noticed, that there IS a current version of Visio provided. I suggest you get updated before writing umbarrasing stuff in the name of your company.



  • Flavelle Ballem

    You will probably need to ask this on a Visio related forum but my assumption is that since the current version of Visio was released a couple years before SQL Server 2005, it's probably not surprising that Visio didn't include provisions for features that didn't exist at the time it was released.
  • PsychicDave

    I'm working on a client's Data Model in Visio 2003 and trying to prepare a physical model. I'm stuck having to read the model and hand code the ddl as there is absolutely no way to print the details, copy and paste, export, not to mention forward engineer the perfectly good model to something useful. Yet I can reverse engineer

    Why would you ever provide the templates and the input capability of a data model and not let me at least get a table and attribute report. We used to call this a "sink" but perhaps the term "black hole" is more in vogue these days.

    There are a good number of us small business developers who can't afford the Enterprise level of software but who need good tools and Visio is certainly the best poor man's tool for creating the model and diagrams.



  • ender080

    I have the same question! Someone @MS please answer!

  • SQL 2005 and Visio for Enterprise Architects Database