SleepyAnt Software

If you work on a project based on a SQL Server database it might be a complex task to handle the evolution of your project database. You can streamline this process with the help of Sync For SQLServer.

• Whenever somebody makes a change to a database object, you create a change script and store it in a source control system.
  
• At the end of the project, you merge all the different scripts and create a large script. You then test the final script on a copy of the production database to upgrade it to the new version. You then debug the script.

But this process has some drawbacks:

• Developers don't always create the scripts when they modify the database. When they do, they don't test them, so they don't work. You end up with many redundant scripts (if a column is added to a table, then removed, that's two unnecessary scripts).
  
• You have no way of knowing if the script has made all the necessary changes. The only way to find out is to test your application and see where it crashes.
• It is extremely time consuming and inaccurate. It costs a lot of time creating and debugging the final migration script. This way you're wasting a massive amount of developer resources performing those tasks.

Automated processes are there to eliminate some kind of primitive work, improve quality and help to keep developers satisfied with their day to day work.

Sync For SQLServer helps you create a professional basis for your database update process. You can try this proved way of working for yourself. Rather than create individual SQL scripts whenever you change a database object, run Sync For SQLServer when you have made all the database changes. It will show you the differences between your development and production databases and create a set of scripts to migrate from one to the other.

It will save you hours of tedious work and you wont have to worry any more about keeping all your databases in sync. Our proved process is a starting point for your own database update process.