Ok... cancel my last. I went to the link posted and they didn't ask for a whole lot (just Name and email address) and so I took a shot at it. First of all, the "Light" and "Blue" display options DO have a nice White background. I did try the "Dark" option. If they had used Black lines on the White background, things would have been great for me but the Blue lines that they use and the font colors are just a little pale on the White background and so, for this particular product, I have to admit the "Dark" background is easier to read.
I also have to say I can't believe they offer this product for free. I've only been playing with it against the Adventure works database for about an hour but I'm impressed with what it does and really like, for example, that it identifies AKs as well as making a line difference between "Identifying" and "Non-Identifying" relationships although I'd have preferred it if they had simply used different colored solid lines instead of dashed lines for "Non-Identifying" relationships. Still, for a free product that does so much, I'm not going to complain.
So far, I like the "Tree" layout the best but they have 5 others depending on what you're used to and they have 4 different "Edge routing" selections (I like "Polyline" the best, so far). And it's super easy and nearly instantaneous to switch between "Tree" and "Hierarchical" to study relationships. Like I said, I can't believe it's free. And, I have it working on old Windows 7 and it very nicely reversed engineered Adventureworks 2008.
I really liked the simplicity of "SQL Diagrams" but I have to admit that ApexSQL Model is simple as simple to use and has a whole lot more power without the danger of accidentally changing the underlying database for "What If" diagrams.
The one thing that I am going to miss (and the product doesn't seem to have a way to do it) is to be able to start a new diagram with just one table and then tell it to add tables to the diagram than have relationships with that one table, like SQL Diagrams did. Gonna miss that a whole lot.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)