In our previous article Advantages of ApexSQL Source Control – Part 1 we presented the most important aspects of ApexSQL Source Control compared to other tools. In this article we will describe additional features found only in ApexSQL Source Control.
By performing a check out in ApexSQL Source Control, a developer can inform others that the object is being worked on through the Object Explorer icon status:
By using ApexSQL Source Control you can start the Object status form (right-click the database in Object Explorer -> ApexSQL Source Control -> Object status) and see who has the files checked out, locked or who has uncommitted changes:
With database policies, we have introduced a possibility to implement a specific workflow to all developers working on a single database. For example, if the Permissive policy is set on a database, no developers can make a change to an object without executing a Check out action against the object that he wants to change. In that way, teams can introduce proper development principles to their development processes.
Using ApexSQL Source Control in the Shared model, you can enable the logging feature which tracks all DDL changes made to the database. By starting up the Change log form (right-click the database in Object Explorer -> ApexSQL Source Control -> View logging), you can filter the data in order to track who changed what and when:
February 19, 2015