Automated DB Source Control (2 of 5): The SSIS Package

Josh,

To continue from the last post, you'll need an SSIS package to drive the process.  This package joins all the steps, running the custom code, the SQL Scripts, and Checking In the changes.  Here's what you came up with...

Automated DB Source Control (1 of 5): Overview and Setup

Josh,

So you've run into a situation where a SQL Database is considered the container of production and/or development code.  You would like to source control all the tables, views, stored procedures, and other database objects.  However, saving the TSQL to the appropriate files/project and checking it in can be very cumbersome.  It would be nice if the developer could just focus on getting the appropriate changes in the database they are working on and let the source control be automatically updated each night.  Here is the solution you came up for this...

Using Custom DLL's in an SSIS Script Task

Josh,

So you've created an awesome class library you want to use in an SSIS package.  Instead of worrying about registering it in the GAC, you can do the following to make sure your code will work in production.

Create C# Classes from JSON

Josh,

So you're working with JSON data and you need to create C# classes to hold the deserialized data.  Naturally you're going to use the JSON.Net library to handle the deserialization, but you would like something to give you a jump start on the C# classes.  You found this json2csharp page that allows you to paste in some JSON and have it generate your C# classes for you.  Now with just a little bit of cleanup you have your working classes!

Generate C# Properties from SQL Table

Josh,

So, you like to design your models in the database but need them in C# as well. To make the recreation in C# quicker, you created a SQL script to convert the table columns into C# Properties.