I use special Auto-changes SQL scripts to control database structure and data of .NET/MSSQL projects. Maybe later I’ll write more about it. Let’s say it’s mostly the set of T-SQL code chunks to provide changes in your local development or live production database or some staging or QA server.In opposite to this single SQL file way, South DB migration tool for Django framework has separated file per each change. We call such change a migration. It’s not SQL file that change something in DB directly, but python module that provide changes via ORM. It’s ok to run pure SQL statements as well. Each migration has 2 ways (methods) forward to go to this migration and backward for jumping to previous migration in the sequence. There is migration sequence may be provided per each Django application. So, the sense is to create migration and then apply it.