Best Approach to Upgrading SQL Database

Our build process is pretty clean with Team Foundation Server. We can create and publish a website in three branches Dev / Qa / Prd. Beyond some fun with web.config (which can help more using .NET 4), this works well.

But on the DB side, everything is not so satisfactory. I script to output all updates and compile them into a single file. Then I send this file to another guy who actually runs the scripts.

Problems

  • AFAIK TFS has weak / poor / no integration with SQL server.
  • I easily skip updating (scripting permissions ...).
  • I do not like to create complex scripts to insert a column into a specific index / serial number.
  • Easy to skip trigger.
  • This is not interesting for test data script.
  • The process is disconnected from our regular build. (Joel tests 1 step build = fail)

I have used Contiuous Integration in the past. Although, I'm not sure how this can help us with SQL. So how can I make the process more automated for SQL?

+3
source share
1 answer

Now you can create a SQL project in Visual Studio that may have some of the functionality you need. To be honest, I just created one of them to just play with it, because my current client is the Java store.

Red Source SQL Source Control. , Red Gate . , ( ), , , , . , , .

+1

All Articles