Now you can keep track of your SQL objects in your favorite version control (Git, TFS, Subversion, SourceSafe, etc), and quickly deploy those changes back to the SQL server.
Control your Tables, Stored Procedures, Views, Functions, Triggers, and much more, in the same way as you control your source code.
Deployment to production can be restricted to version controlled scripts and controlled changes. Developers don't need access rights on production servers anymore. Auditors can trace the responsible for each change.
DBAs or Data Administrators can easily review the differences before running scripts in production environment. No need to review a huge script for every small change.
Some nice features that will facilitate your work:
Servantt Lite is a freeware tool for helping you correctly keep your SQL objects into source control.
It is fully functional, does not have any limitation, and is free for personal and commercial use. And will always be free.
Servantt Professional is a totally different beast, a more complete product targeted at deployment automation.
It's in final development phase and will have very different features:
Subscribe to get access to our product beta!
Feedback from the first users has been awesome!
Keeping SQL objects into Source Control has never been so easy! I loved the WinMerge feature, it won't let you forget any changes in your development database.
That's a great tool for companies where developers cannot apply scripts to production. Much easier (and yet more useful) than SQL Management Studio scripting.
Now when developers send me scripts to run in production environment I can review their changes (mostly for performance and naming standards) and prepare rollback scripts in a few minutes! That was so much more difficult before.
Servantt Professional allows enterprises to update their server applications with no pain. With an intuitive interface you can plan the deployment steps, get management approvals, and quickly upgrade your apps into your production and staging servers.
You don't need to setup Continuous Integration, develop complex branching processes, or even change your app versioning processes. Developers don't need to create installers/uninstallers for every single update.
You can continue working exactly as you do (even with legacy technologies!)- it just works.
You don't need to learn a new programming language, design complex workflow, edit XML files, or debug scripts.
Everything is designed through interfaces identical to the ones that you already use. Do you know how to use Windows Explorer, Copy-Paste, SQL Server? That's all you need
You don't need to develop custom deployment scripts just for updating frequently modified SQL artifacts, like stored procedures, views and functions.
SQL artifacts are deployed exactly like files: backup of previous revisions are made, artifacts are automatically updated, and rollback quickly restores previous revisions if needed.
It's not an automation toy that only Software Engineers could understand and benefit from.
It has full management features that allow highly-configurable permissions and approval for Change Managers, Server Administrators, Database Administrators, and much more. Track all deployments, comply with audit requirements, and mitigate risks easily.
Frequent software releases are important for most companies to stay competitive, and also important for dealing with highly-demanding users. Release processes tipically involve multiple roles, such as the developers (software engineers), the change manager and committee, operations team (network administrators), and database administrators. This is usually a very tedious, slow and repetitive process, in which the main risk is human error, not only in the planning phase but more frequently during the execution phase. Automation will shorten your release cycle, allowing you to deliver more features, reducing drastically the cost of releases and reducing downtime both for executions and rollbacks.
Other deployment solutions are generic automation/workflow tools that propose to automate every kind of operation in your datacenter, including first-time-installations, database maintenance, and everything else. Obviously, the price to pay for such a a generic solution is that it's extremely difficult to design even basic tasks.
Servantt is focused only in updating existing applications, which obviously is much more frequent than first-time installations, and is exactly the critical activity where you need to avoid errors and reduce downtime.
Since planning a deploy is a piece of cake, developers can focus on what they do best: develop software!