I am looking at how I would be able to use VS SQL Server 2005 projects,
however I am having difficulty seeing how I can build deploy to the live
environment.

As an example, I have an existing DB in production which I want to upgrade
to the new build. Upon building the project a SQL script is produced for
creating a new DB,however this is not what I require, I need a way of
updating the existing production database to reflect the new schema leaving
any existing data intact.

Could anybody point me in the correct direction of how I should be doing
this? I could do this as a manual process, however I was hoping that the VS
project would allow me to automate this script creation.

Thanks

> Could anybody point me in the correct direction of how I should be doing
> this? I could do this as a manual process, however I was hoping that the
> VS
> project would allow me to automate this script creation.

I believe you'll need the Database Edition of Visual Studio Team System in
order to facilitate upgrade automation. AFAIK, schema upgrades must be done
manually with other editions of VS.

--
Hope this s.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"StrictlySocial" <StrictlySocial@discussions.microsoft.com> wrote in message
news:79AF4EED-50CB-4549-B2C2-40678CB92984@microsoft.com...
>I am looking at how I would be able to use VS SQL Server 2005 projects,
> however I am having difficulty seeing how I can build deploy to the live
> environment.
>
> As an example, I have an existing DB in production which I want to upgrade
> to the new build. Upon building the project a SQL script is produced for
> creating a new DB,however this is not what I require, I need a way of
> updating the existing production database to reflect the new schema
> leaving
> any existing data intact.
>
> Could anybody point me in the correct direction of how I should be doing
> this? I could do this as a manual process, however I was hoping that the
> VS
> project would allow me to automate this script creation.
>
> Thanks

Hi,

Sorry I wasn't very clear, I have 2008 VTS which includes DP. I can deploy
my release to the local/networked machines - however the issue I have is that
I don't have access to the production environment (network restrictions).
Therefore I was looking for an automated method (if possible at all) whereby
I could produce an SQL update script outlining the differences between last
production release and the current dev db.

I am guessing that the only way I can do this is by installing the
production schema locally, then performing a schema comparison between DEV
and Production (local). It's just a shame that I have to do this manually and
can't somehow get this to occur as part of the build process.

Regards


"Dan Guzman" wrote:

> > Could anybody point me in the correct direction of how I should be doing
> > this? I could do this as a manual process, however I was hoping that the
> > VS
> > project would allow me to automate this script creation.
>
> I believe you'll need the Database Edition of Visual Studio Team System in
> order to facilitate upgrade automation. AFAIK, schema upgrades must be done
> manually with other editions of VS.
>
> --
> Hope this s.
>
> Dan Guzman
> SQL Server MVP
> http://weblogs.sqlteam.com/dang/
>
> "StrictlySocial" <StrictlySocial@discussions.microsoft.com> wrote in message
> news:79AF4EED-50CB-4549-B2C2-40678CB92984@microsoft.com...
> >I am looking at how I would be able to use VS SQL Server 2005 projects,
> > however I am having difficulty seeing how I can build deploy to the live
> > environment.
> >
> > As an example, I have an existing DB in production which I want to upgrade
> > to the new build. Upon building the project a SQL script is produced for
> > creating a new DB,however this is not what I require, I need a way of
> > updating the existing production database to reflect the new schema
> > leaving
> > any existing data intact.
> >
> > Could anybody point me in the correct direction of how I should be doing
> > this? I could do this as a manual process, however I was hoping that the
> > VS
> > project would allow me to automate this script creation.
> >
> > Thanks
>
>

> I am guessing that the only way I can do this is by installing the
> production schema locally, then performing a schema comparison between DEV
> and Production (local). It's just a shame that I have to do this manually
> and
> can't somehow get this to occur as part of the build process.

Yes, you'll certainly need a copy of the prod schema for the compare. You
might take a look at VSTSDB 2008 GDR CTP16
(http://blogs.msdn.com/gertd/archive/...6-is-here.aspx).
I haven't had a chance to play around with it myself but it looks like this
can be integrated into an automated build database process.

--
Hope this s.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"StrictlySocial" <StrictlySocial@discussions.microsoft.com> wrote in message
news:B3FF365E-D0BA-464A-A8D9-391B991BE5ED@microsoft.com...
> Hi,
>
> Sorry I wasn't very clear, I have 2008 VTS which includes DP. I can deploy
> my release to the local/networked machines - however the issue I have is
> that
> I don't have access to the production environment (network restrictions).
> Therefore I was looking for an automated method (if possible at all)
> whereby
> I could produce an SQL update script outlining the differences between
> last
> production release and the current dev db.
>
> I am guessing that the only way I can do this is by installing the
> production schema locally, then performing a schema comparison between DEV
> and Production (local). It's just a shame that I have to do this manually
> and
> can't somehow get this to occur as part of the build process.
>
> Regards
>
>
> "Dan Guzman" wrote:
>
>> > Could anybody point me in the correct direction of how I should be
>> > doing
>> > this? I could do this as a manual process, however I was hoping that
>> > the
>> > VS
>> > project would allow me to automate this script creation.
>>
>> I believe you'll need the Database Edition of Visual Studio Team System
>> in
>> order to facilitate upgrade automation. AFAIK, schema upgrades must be
>> done
>> manually with other editions of VS.
>>
>> --
>> Hope this s.
>>
>> Dan Guzman
>> SQL Server MVP
>> http://weblogs.sqlteam.com/dang/
>>
>> "StrictlySocial" <StrictlySocial@discussions.microsoft.com> wrote in
>> message
>> news:79AF4EED-50CB-4549-B2C2-40678CB92984@microsoft.com...
>> >I am looking at how I would be able to use VS SQL Server 2005 projects,
>> > however I am having difficulty seeing how I can build deploy to the
>> > live
>> > environment.
>> >
>> > As an example, I have an existing DB in production which I want to
>> > upgrade
>> > to the new build. Upon building the project a SQL script is produced
>> > for
>> > creating a new DB,however this is not what I require, I need a way of
>> > updating the existing production database to reflect the new schema
>> > leaving
>> > any existing data intact.
>> >
>> > Could anybody point me in the correct direction of how I should be
>> > doing
>> > this? I could do this as a manual process, however I was hoping that
>> > the
>> > VS
>> > project would allow me to automate this script creation.
>> >
>> > Thanks
>>
>>