Database Diagrams, Feedback and Usage
Database Diagrams in SQL Server 2005 and VS 2005 were one of the more *ahem* controversial issues. If you remember at one point they were cut, then they came back, mostly as a result of the overwhelming feedback on them.
Well (Data Dudette) Mairead now owns them and is looking for feedback, here is the entry to respond to.
Comments
- Anonymous
February 23, 2007
The comment has been removed - Anonymous
March 22, 2007
A few comments to expand on David Harrison's feedback:
- The application crashes surprisingly often when working on diagrams. Frequent Save is essential.
- Page setup is necessary every time I start an editing session. It forgets that I am drawing on 11x17 sheets.
- Printing a page that is not at 100% zoom gives unpredictable output. Tables are rerendered and scroll bars reappear as rows disappear.
- When you change zoom level, you need to slide the window around so that tables pass out of view and get rerendered.
- Printed tables look like there is a missing font. The left column boxes are partly shaded, and there is a strange multi-shaded band below the last row in the table.
- I have had to stretch the layout of all of my SQL 2000 diagrams because rows in tables are now depicted with more height. This is a very weak visual layout tool. Do the SQL Server folks know that Microsoft acquired Visio several years ago?