What have you been working on?
- We have been working on bug fixes, improving usability and general quality along with introducing several new features
- The user will have the ability to place custom scripts under source control. With this feature the user will have the ability to add scripts and/or script folders under source control so that changes can be tracked in the same way as for SQL objects. This can be used in cases where some important files should be versioned along with the database
- A new database policy was created which will be responsible for allow/prevent committing changes made by other users
- Users will have the ability to choose where the working copy of the repository will be placed on a local file system
- Usability of the Change log feature is improved by showing T-SQL scripts of all changes made on the database in the Change log form. Before this feature, users were able to see only who did the change, when and on which object, without the ability to see what is changed.
- Other than native support for the most popular source control systems, we’ve introduced the ability to use any source control system that supports the Command Line Interface.
Those features will be included in ApexSQL Source Control R10 along with SQL Server 2016 CTP2 support, SQL Server Management Studio 2016 CTP2 integration and Azure SQL Database support
What is the ETA to production?
- ApexSQL Source Control R10 will be released in first half of November
- For a complete schedule of all upcoming releases, please see the Product roadmap
What usability issues have you encountered and overcome?
- From ApexSQL Source Control R10 the user will be able to choose where the working copy of repository will be placed on local file system.
Users will be able to allow/prevent committing changes made by other users from the ApexSQL Source Control Options:
- We have improved the usability of Change log feature. From ApexSQL Source Control R10 users will have the ability to see what is change on each object through T-SQL script
What are some features planned in the next release(s) and what are their ETAs?
ApexSQL Source Control 2015 R10 – Q4:
- SQL Server 2016 CTP2 support.
- SQL Server Management Studio 2016 CTP2 integration.
- Azure SQL Database support
- CLI support for major source control systems
- Ability to place folder with scripts under source control
- Database policy responsible for allowing/disallowing committing changes made by other users
- Ability to choose working copy of repository location on local file system
- Ability to see T-SQL script for every change in Change log form
ApexSQL Source Control 2016 R1 – Q1:
- SQL Server 2016 support
- SQL Server Management Studio 2016 integration
- Support for migration scripts – Migration scripts are SQL scripts that are attached to a specific schema change and need to be executed before the change is applied in order to preserve data or set the required server settings
ApexSQL Source Control 2016 R2 – Q2:
- Support for basic branching and merging functionalities – Although we have a workaround for those features, our plan is to allow the users to create a branch or to merge two branches within a simple click
- Support for association with the work item by ID – Other than comments whose main purpose is to inform other users about the reason for changes, we are planning to introduce the ability to associate the specific changes with work items
September 23, 2015