Once you've exported the scripts for the first time and added them to you're
repository, the only discipline required is open the file from your
repository instead of from the database. You can still use Enterprise
Manager essentially the same way you do today.
On 10/5/07, Janca, Tanya <TJanca@justice.gc.ca> wrote:
>
> Hello all,
>
> We are using Enterprise Manager to edit our stored procedures. We are
> starting a new project and considering all of our source control options. Is
> there a way to integrate subversion into MS SQL Server 7 to edit our stored
> procedures. We currently use Enterprise Manager for editing... We do not
> want to have to export our scripts one by one, check them into a source
> control program, and then discipline ourselves to check them out, edit them
> in our database, test them, export and copy into our source control text
> files, then check them in again. It's quite tedious, and could easily end up
> creating a mess. =3D20 =3D20 The = only fully-integrated option we have come
> up with so far is to get .Net 2005 TEAM Edition and MS Visual Source Safe,
> then editing our stored procedures with the .Net. The two apps fully
> integrate for stored procedures, but only the team edition, not the pro
> edition that we already own licenses to... An upgrade with all new licenses
> is expensive. We are looking for a more economical solution. Is subversion
> it?
>
> Thanks
>
> Tanya
>
---------------------------
www.maf.org/rhoads
www.ontherhoads.org
Received on Fri Oct 5 21:15:07 2007