Home/ Questions/Q 134485
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T06:37:19+00:00

Mostly we change existing database tables, stored procedures, functions or parameters in tables for

  • 0

Mostly we change existing database tables, stored procedures, functions or parameters in tables for software upgrades/bugfixes. And when it’s time to deploy our changes to another environment like production or preproduction, some parts of our db changes are forgotten.

In our company, some developers use a database difference analysis application to find out the differences between test and production environment. Some developers store t-sql of every change they made on db, like me.

I wonder what are you doing to deploy db changes to production environment. Why you choose that way ? Or what must be done ?

Thanks for the replies !

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. We have our db under Source Control. Any changes are tracked that way. Anything else would be a nightmare.

    Jeff has an article on it too – http://blog.codinghorror.com/get-your-database-under-version-control/

    SQL Server has the Generate and Publish Scripts Wizard, which can be really useful if you want to put an existing database into source control.

    • 0