Database patching.

Hi Everyone.
The company that I work for have a database, which needs patching every so
often from one version to the next. We've been trying different methods of
upgrading the database from one version to the next. But each idea that
we've tried has been difficult, clunky or just plain stressful. Anyway, in
order to ease the process of patching both Schema and data there must be a
way of doing this which is painless and easy to accomplish.
Does anyone have any suggestions that are worth checking out?
Regards
Colin Dawson
www.cjdawson.com"Colin Dawson" <newsgroups@.cjdawson.com> wrote in message
news:hzWLf.26203$wl.25912@.text.news.blueyonder.co.uk...

> Does anyone have any suggestions that are worth checking out?
Not too sure what your problem is... I do this sort of thing all the time
with nothing more than T-SQL. The only thing you need to be careful of is
making the schema and/or data modifications in the right order...|||Colin Dawson wrote:
> Hi Everyone.
> The company that I work for have a database, which needs patching every so
> often from one version to the next. We've been trying different methods
of
> upgrading the database from one version to the next. But each idea that
> we've tried has been difficult, clunky or just plain stressful. Anyway,
in
> order to ease the process of patching both Schema and data there must be a
> way of doing this which is painless and easy to accomplish.
> Does anyone have any suggestions that are worth checking out?
> Regards
> Colin Dawson
> www.cjdawson.com
What is your existing process and what exactly is the problem? For
incremental fixes one might expect:
- Unit-tested change scripts checked into source control
- Release script compiled from an amalgamation of the change scripts
- Release to a test environment for system and regression testing
- Release to a UAT environment (to include testing by production
support if appropriate)
- Release to production
If you need help compiling and validating the scripts then check out
some software like the RedGate compare tools: www.red-gate.com
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Hi all.
Just to elaborate a little, I'm an architech for a team of 20 developers.
They're always making stored procedure changes and schema changes, basically
the problem is that it's happening so fast that I'm not able to keep up.
What I want to be able to do is skip checking, diagnosing every single
little change, and pile them into one large change script which I can then
check quicker.
Ideally, I really suppose that I'm looking for some kind of Silver Bullet.
I know that there is rarely anything that will solve problems like this.
But there's always hope.
Regards
Colin Dawson
www.cjdawson.com