Blog Post

T-SQL Tuesday #90 – Shipping Database Changes

T-SQL Tuesday 90

I was once asked to add a new feature to an application. It was installed on multiple SQL Server instances across multiple physical sites. The problem was that different instances of the application had different database schemas. New code may work on my local schema, but it could fail on the different schemas in live.

To develop the feature, I knew that I needed one universal version of the database schema.

I merged the schemas into a version that met the requirements of all environments and redeployed. Once in source control, this schema became the single source of truth that all future deployments were built from.

Not only did this solve my problem, it served as the foundation for the automation of builds, tests and deployments.

I’ve been interested in Continuous Integration and Database Lifecycle Management ever since. For more details, check my series of posts that start with SQL Server & Continuous Integration.

For this T-SQL Tuesday, I’d like to hear about your thoughts or experiences with database deployments.

Read the rules below and join in by publishing a short post about database deployments. If you develop or deploy database changes, I want to hear about it.

Your post can cover anything related to database deployments, but if you need inspiration, feel free to cover any of the topics below:

I look forward to reading your post!

The Rules

Publish your blog post on Tuesday, the 9th of May 2017. The post needs to include the T-SQL Tuesday logo on the right, and a link to this invitation post. Read the T-SQL Tuesday Rules and don’t forget to add #tsql2sday to any tweets about your post.

Leave a comment on this post with a link to your entry. I’ll publish a roundup post on the 16th.

Want to host your own T-SQL Tuesday? Email Adam Machanic at amachanic at gmail dot com and volunteer. I did just that and here I am.

The post T-SQL Tuesday #90 – Shipping Database Changes appeared first on The Database Avenger.


You rated this post out of 5. Change rating




You rated this post out of 5. Change rating