Getting objects in existing DBs into VSS

What is the easiest way, in SQL Server 2005, to get all my existing
database objects (procs/views/tables, etc) scripted and into
Projects/Solutions/VSS?I always take the following steps with SQL Server 2000:
With the Enterprise manager, Right-click on the database in the main
window and choose All tasks - Generate SQL Script. In this dialog,
choose to script all objects and choose to generate 1 file per object.
I would recommend to check all options like generating primary keys,
permissions, etc.
This will generate a lot of files in a single directory. With the
Source Safe client, just add all files from the working folder to your
Source Safe project. Now you can track changes per database object. If
you want to do this again some time later, just check out all files in
Source Safe before scripting and make sure you add new object and
delete objects form Source Safe that do no longer exists (or changed
names).
Of course, this will not create any data scripts, just object
definitions.
I am pretty sure you could achieve something like this using SQL Server
2005.
cbtechlists@.gmail.com schreef:
> What is the easiest way, in SQL Server 2005, to get all my existing
> database objects (procs/views/tables, etc) scripted and into
> Projects/Solutions/VSS?|||2005 doesn't support scripting one object per file but a
utility has been written to do this. Check the following:
http://weblogs.sqlteam.com/billg/archive/2005/11/22/8414.aspx
-Sue
On 2 Oct 2006 13:17:51 -0700, "Roel Schreurs"
<roel.schreurs@.gmail.com> wrote:
>I always take the following steps with SQL Server 2000:
>With the Enterprise manager, Right-click on the database in the main
>window and choose All tasks - Generate SQL Script. In this dialog,
>choose to script all objects and choose to generate 1 file per object.
>I would recommend to check all options like generating primary keys,
>permissions, etc.
>This will generate a lot of files in a single directory. With the
>Source Safe client, just add all files from the working folder to your
>Source Safe project. Now you can track changes per database object. If
>you want to do this again some time later, just check out all files in
>Source Safe before scripting and make sure you add new object and
>delete objects form Source Safe that do no longer exists (or changed
>names).
>Of course, this will not create any data scripts, just object
>definitions.
>I am pretty sure you could achieve something like this using SQL Server
>2005.
>
>cbtechlists@.gmail.com schreef:
>> What is the easiest way, in SQL Server 2005, to get all my existing
>> database objects (procs/views/tables, etc) scripted and into
>> Projects/Solutions/VSS?|||Thanks.
I've got everything scripted out individually in my SQL Server 2000
database, but I'm still trying to figure out how to setup the Projects
& Solutions in SQL Server 2005 so that they are organized by type (e.g.
procs, views, tables, udfs, etc). I don't seem to be able to add my own
folders to organize things.
I want to be able to open SS 2005, select an object from the solution
explorer, check it out of VSS 2005, modify it, execute it, and check it
back in with update information. Same with creating objects.
Do you have a process that works for you? How do you go about making
sure that you always check out/check in your scripts? Are there any
good articles that describe this aspect of management?
Thanks!
Chris|||Thanks.
I've got everything scripted out individually in my SQL Server 2000
database, but I'm still trying to figure out how to setup the Projects
& Solutions in SQL Server 2005 so that they are organized by type (e.g.
procs, views, tables, udfs, etc). I don't seem to be able to add my own
folders to organize things.
I want to be able to open SS 2005, select an object from the solution
explorer, check it out of VSS 2005, modify it, execute it, and check it
back in with update information. Same with creating objects.
Do you have a process that works for you? How do you go about making
sure that you always check out/check in your scripts? Are there any
good articles that describe this aspect of management?
Thanks!
Chris