Hi
If your code had been under source code control you would not be asking the
question! Using a script generator will work fine in this instance, but if
you expand the number of production systems, then you may end up having to
generate bespoke scripts for every single one, if things are not controlled
correctly. Not having version control will mean that you are potentially
going to loose code and introduce old bugs, these sorts of errors will not
only cost you time to sort out, but may be difficult to trace if you are
assuming that they have a particular environment.
What ever method you choose to implement you should test the upgrade process
before hand.
John
<Dj********@lund.cc> wrote in message
news:11*********************@l41g2000cwc.googlegro ups.com...
Hi,
I have a SQL server DB for a document handeling system.
For the new version of the system the database have been updated with
some new tables, new stored procedures and updated stored procedures.
There is no changes in the existing tables that contains data.
What is the best way to update this DB?
I had planned to use the SQL script generator. Is there a problem with
this?
The database is not version controlled by VSS as the app code. The
database have just been scripted with the generator at the release of
the version and saved. But this is the first time when there is
production data in the DB.
Thanks in advance!
