I'm looking for advice as to the best approach for redesigning our data infrastructure & bringing it into SQL Server. This would include data modeling, redesign of existing .dbf tables, analysis of relationships, inclusion of not-yet-existing tables into the whole mix, generation of DDL scripts, etc. Tools like ERWin, etc., at out of the picture due to cost. XCase or Visio Enterprise Architect might be possibilities. Given those two tools (or ones of similar price level and capabilities), or just using the SQL Server Mgmt Studio to design "test" databases first - what do you recommend & why?

Thanks much, Randy

how many tables? if the answer is under a hundred, use paper and pencil, then write the DDL directly in a text editor (it's easy once you understand which sequence to declare the tables in)

or mock it up in access (which has a great front end), and upsize

There are currently probably 200-300 or more tables, and more will be added.