What is the point of using a “real” database modeling tool?

Question

We currently have a 10-year-old disgusting spaghetti-style SQL Server database, which we will be rewriting from scratch soon, as part of rewriting into a large web application. (The existing application will serve as functional requirements for the next implementation of the application).

Some of them suggested that we use Visio to run all the diagrams and create DDL, but others suggested using a special tool to create a database, rather than a diagram tool that can export DDL.

Is there any use to using "real" database design tools like ModelRight over common tools like Visio? If so, what are these specific benefits?

---

Editing: in short, what real / dedicated tools can do, something like Visio can't and how much do these features matter and / or are they worth it? (in terms of best practices, for example)

Answer 1

. . , . , , .

, . , .

, , , , .

, Eclipse Visual Studio , .

ER . ( ?).

, , , ER :

• .
• , , .
• .
• .
• SQL.
• , .
• , ( , , ...) .
• , , (), (first_nm) . -, .
• .

ERWin, MySQL Workbench ER/Studio - , , , , . . , .

ERWin , , .

Visio .

, .

Answer 2

Visual Studio 2008, , SQL Server 2005. ( SSMS) script. . .

Answer 3

Oracle - Enterprise Elements
, , . " ", - .. , ,

Answer 4

, . ( ), , , .

, Enterprise Manager ( , Management Studio) Visio.

Answer 5

MySQL Workbench.

http://en.wikipedia.org/wiki/MySQL_Workbench

http://wb.mysql.com/

Answer 6

, , , , Visio:

• alter script ,

, , , , .

Answer 7

, , DDL . " ", , ; , , , . - , , . , ErWin, StarDesigner ...

If your database is located exactly where your business layer stores its data, and the database is not a key driver for the project (as a rule, this applies to web applications), I would not talk too much about it - you will get much a bigger take-off for the dollar, looking at the continuous integration with the database and other ways of developing the database during the development process.