for the record; Visual Studio isn't as powerful as 'Microsoft Access'
is for writing stored procedures.
plus VS and Visual Source Safe costs an assload.
like.. 3 grand or something.
you could buy a new server for that much
-Aaron
[quoted text, click to view] Lee Boozer wrote:
> Use a database project in Visual Studio (which integrates seamlessly with Source
> Safe). Make all code changes in a development environment, then migrate them to
> your other environments via a controlled process (i.e. DBA applies database
> change scripts).
>
>
> On 6 Dec 2006 22:02:31 -0800, "Mehdi" <m_khajeh57@yahoo.com> wrote:
>
> >Dear
> >In our company, we use sql server 2000 as the database server for
> >softwares we produce. The problem is the way that we track the changes
> >in database and control the changes which every developer makes in db
> >(something like source safe that controls the code changes for our
> >source codes) . I would like to learn (and ofcourse use) about
> >processes of change control for sql server databases and so on...
> >Do you know any idea or resources about that?