Database Diagramming Kano Survey (by Tim)

We're rerunning our database modeling survey in Kano format.  If you're interested in the future of data modeling in VS and the SQL Server tools, then we'd appreciate your help in defining what we build.  Please fill out the survey posted at:

Thanks in advance for your time and help!

- Tim Laverty

Comments (5)
  1. Grant Case says:

    Tim I just replied to the survey but I will reply here as well because 1000 characters was not enough to say everyone I wanted.

    Database Design Rule Sets – Along the lines of things that would be great to have that would seriously reduce Microsoft headaches from users would be to look at the Microsoft SQL Server Best Practices Analyzer. I would really like to create a set of rules for the data models and then be able to share and enforce those rules. You could create your own rules for naming conventions thus leaving Microsoft not having to worry about this. Examples of rules could be foreign keys must have the same name, no varchar fields greater then 250, etc.

    Data dictionary and Annotations – This is a requirement going forward and it’s a joke that Visio cannot address the extended properties within SQL Server. this is all I need in terms of a dictionary but it would be really nice to annotate my design by spawning Word, edit, then save and have the information re-imported into the model (RTF only, no pics). All this would print out in a nice HTML help file like SQL Scribe, which I can hand out to the developers.

    Macros – Every other Microsoft application has the ability to write and record macros this one should be the same.

    Track Model Changes – I am thinking along the lines of Word’s ability in this area. This could help a great deal because we generally do not comment table creation and changes. This would be a nice feature to have and would allows us to understand why design changes were made.

    Wizards – I am database professional, I do not need a wizard on how to create a table or a view nor will the people who use this application. Let’s assume some prior knowledge of database design when building this application. Do NOT design for the lowest denominator.

  2. Fred Pugsley says:

    I just replied to the survey. This is a vital area for Microsoft dev tools. Please follow up with some more contact, as I have much more input to give on this issue.

  3. Andy Mackie says:

    The survey does not include PowerDesigner in the list of modeling tools. Either add this, or add a checkbox for "Other tool", and have a textbox to enter the name.

    Generating SQL scripts for multiple DBMS’s from a single model is a must (Oracle, SQL Server, DB2 etc.). If it’s SQL Server only, then I couldn’t use it. The world is heterogenous, whether we like it or not.

    Dare I ask about a release date ? I’d guess if you are still at the prioritizing requirements stage, it would be at least a year away (if not longer).

    Other thoughts: Support for relational-domains (probably map to user-defined datatypes with check constraints in DB), reporting to HTML/Word essential, export of diagram, support for comments which get included in DB (extended properties), specifying object-owners, alternate keys, data-dictionary, multiple notations supported (UML, "crows-foot", IDEF1X, etc.) which can be changed anytime, the list goes on. I’m sure you’ve reviewed the features of other tools such ERWin, PowerDesigner, ER/Studio.

    Please ensure this is a "proper" modeling tool, and not a toy like Database Diagrams in SQL Server! Good luck!

  4. Tim Laverty (MS) says:

    <<Fred Pugsley –

    I just replied to the survey. This is a vital area for Microsoft dev tools. Please follow up with some more contact, as I have much more input to give on this issue. >>

    Fred, can you send me an email: so we can chat. I don’t see your email in the survey data.

Comments are closed.

Skip to main content