Schema Update Mechanism

[Guest]

Was looking for some advice with respect to keeping schemas up to date.

Here's the situation:

- Specialized application is in production at client site
- Continually making additions/enhancements to application and patching into production system
- On occassion the schema will change on the development side

Up to now, we've been tracking all of the changes made to the schema via a database where we log the
changes. When we put into service the updates, we manually make the changes to the production database.

This basically sucks, as it is prone to error as well as not being the most efficient. Question is, what tools are
you guys using to manage these things? Ideally, I'd like to find a tool that allows for me to generate a SQL
script that we could run on the development database (where all of the testing has taken place) and then
perform this script against the production database, thus ensuring that we don't miss anything.

FYI: The databases in use are Jet, MSDE and SQL Server.

Michael

 

[Arvin Meyer]

SQL-Server can generate SQL scripts to build tables, and you certainly can
write scripts to add columns. You can do the same with DDL scripts in
Access/JET, but I prefer just to export the changes to an empty database and
then import them into a production database. I don't forget anything that
way.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

Was looking for some advice with respect to keeping schemas up to date.

Here's the situation:

- Specialized application is in production at client site
- Continually making additions/enhancements to application and patching into production system
- On occassion the schema will change on the development side

Up to now, we've been tracking all of the changes made to the schema via a database where we log the
changes. When we put into service the updates, we manually make the

changes to the production database.

This basically sucks, as it is prone to error as well as not being the

most efficient. Question is, what tools are

you guys using to manage these things? Ideally, I'd like to find a tool

that allows for me to generate a SQL

script that we could run on the development database (where all of the

testing has taken place) and then