I used pencil and paper quite successfully to get the initial entities and relationships down. Especially good if designing with other people, you don't get distracted by the GUI interface, mousing around, getting the background gradients right, etc. Then you can translate it into Visio or Dia or a UML tool that generates both the SQL Schema and your object model...
Usually after this time constraints mean you end up in TOAD or your DB tool of choice getting the tables, indexes, foreign keys and stuff implemented in straight SQL or with their table designer tool. Changes will inevitably come up downstream so don't spend too long getting things exactly, just get the structure right.
I tend to use SQL Server Management Studio also for quickly doing stuff, but when I am doing the actual implementation or more advanced stuff I use EMS Sql Manager. It is quite a nice tool with far more advanced and more numerous features than Sql Management studio. You can think of it as MS SQL Management Studio on steroids. Takes a bit of getting used to the UI though, but still straight forward enough. And if you get their package with all their peoducts you get a ton of great utilities as well.
You can draw ERDs using GraphViz records. That will not trak/organize your metadata, geneate your DDL or anything else for that matter - but it will give you an entity relationship diagram that you can easily edit/update.
It will handle all the layout/arrangement details of the diagram for you. It does a pretty good job of this. It is sort of a declarative diagram-drawing language. Very simple to learn. Requires nothing but a text editor to use. Many applications use its abilities behind the scenes to generate their diagrams also.
If it is for SQL Server I like the DB Diagram from SQL Server Management Studio.
I used pencil and paper quite successfully to get the initial entities and relationships down. Especially good if designing with other people, you don't get distracted by the GUI interface, mousing around, getting the background gradients right, etc. Then you can translate it into Visio or Dia or a UML tool that generates both the SQL Schema and your object model...
Usually after this time constraints mean you end up in TOAD or your DB tool of choice getting the tables, indexes, foreign keys and stuff implemented in straight SQL or with their table designer tool. Changes will inevitably come up downstream so don't spend too long getting things exactly, just get the structure right.
I tend to use SQL Server Management Studio also for quickly doing stuff, but when I am doing the actual implementation or more advanced stuff I use EMS Sql Manager. It is quite a nice tool with far more advanced and more numerous features than Sql Management studio. You can think of it as MS SQL Management Studio on steroids. Takes a bit of getting used to the UI though, but still straight forward enough. And if you get their package with all their peoducts you get a ton of great utilities as well.
If its just diagramming thoguh i will use Visio.
ModelRight, from http://www.modelright.com is very good for physical modeling. Excellent support for Oracle, MySQL, SQL Server, etc.
try http://www.fabforce.net/dbdesigner4/ for MySQL
You can draw ERDs using GraphViz records. That will not trak/organize your metadata, geneate your DDL or anything else for that matter - but it will give you an entity relationship diagram that you can easily edit/update.
It will handle all the layout/arrangement details of the diagram for you. It does a pretty good job of this. It is sort of a declarative diagram-drawing language. Very simple to learn. Requires nothing but a text editor to use. Many applications use its abilities behind the scenes to generate their diagrams also.