Kilo team update: ApexSQL Script

What have you been working on?

We have been working on implementing support for Azure SQL Database V12 and SQL Server 2016, adding a new “Save as batch” feature, fixing bugs, improving CLI, and improving usability and quality of ApexSQL Script.

What is the ETA to production?

ApexSQL Script 2016 R1 was released to production on May, 10^th, 2016.

What is included in the new release?

• Save as batch – step in Scripting wizard that enables project and its settings as batch file

  

• Script execution results window – Show detailed list of Executable installer’s actions and their status

  

• Improved CLI – with 5 new switches :

  • /filename – name of scripted file,

  • /sourcecontrol_depot –depot for the Perforce source control system,

  • /sourcecontrol_workspace – workspace for the Perforce source control system,

  • /db_compatibility_level –setting the desired compatibility of the extracted files with the specific SQL Server version and

  • /sourcecontrol_branch – branch in Git repository

• Database compatibility – enables setting the compatibility with SQL Server version of the scripted database

  

• SQL Server 2016 and Azure SQL Database V12 support

What is planned in future releases and what are ETAs?

We are currently working on ApexSQL Generate. We are working on implementation new predefined generators, fixing bugs, and improving CLI support and return codes.

We plan to release ApexSQL Generate in early July.