> Am I missing something obvious in the 2005 Visual Studio
> portion of SQL Server?

> I have a database design, with a bunch of tables, views,
> stored procedures, etc, etc. I want to store each object
> in a separate file, so I can keep them in Source Safe.
>
> Is there a command that will "rebuild" the database,
> issuing the CREATE TABLE, VIEW and PROCEDURE statements
> in the "right" order, such that foreign keys, and procedures
> that call procedures get built in the right order?
>
> I know that for tables/views, I could put every in a
> CREATE SCHEMA, but then everything's in one file.

Eric J. Holtman wrote:
> Am I missing something obvious in the 2005 Visual Studio
> portion of SQL Server?
>
> I have a database design, with a bunch of tables, views,
> stored procedures, etc, etc. I want to store each object
> in a separate file, so I can keep them in Source Safe.
>
> Is there a command that will "rebuild" the database,
> issuing the CREATE TABLE, VIEW and PROCEDURE statements
> in the "right" order, such that foreign keys, and procedures
> that call procedures get built in the right order?
>
> I know that for tables/views, I could put every in a
> CREATE SCHEMA, but then everything's in one file.
>
> I've done this the hard way before (isql to get sysdepend
> information, pipe through tsort, build the tables that way),
> but was hoping for a more integrated solution.
>