ApexSQL DevOps toolkit - TeamCity plugin release notes

Fixes:

• Blob columns are ignored when the NuGet package with static data is created in the Package step

Enhancements:

• Provision a database
• Backup database
• Compare production database with source control
• Validate schema changes
• Format and obfuscate SQL code
• Sync step can be sourced directly from source control
• Sync data step can be sourced directly from source control

Fixes:

• “Additional parameters field contains invalid value” error is encountered when a CLI parameter that has space delimited arguments is added
• Static data is included in the package when the Include static data option in the Build step is unchecked

Changes:

• Control to change the source for the Sync step is now a select box
• Control to change the source for the Sync data step is now a select box
• Data sync step is now Sync data step
• Schema sync step is now Sync step

Enhancements:

• Support for TeamCity 2018.1.3 (build 58658)

Fixes:

• Package step extracts synthetic data from the test database when script folder is created

Enhancements:

• Environmental variable %apexsql.outputPath% is added to use as the current execution output path
• The “Exclude tables” option is added in the Audit step

Changes:

• ApexSQL Trigger project file is now mandatory in the Audit step in order to provide audit architecture and repository database information
• ApexSQL Enforce rulebase file upload is replaced with the file path text box in the Review step
• Audit step no longer overwrites existing table triggers
• Separate output folder is created for each consecutive build
• SQL Server and database connection parameters are no longer mandatory when project file is used

Changes:

• ApexSQL CI/CD toolkit – TeamCity plugin name is changed into ApexSQL DevOps toolkit – TeamCity plugin

Features:

• Continuous integration:
  • Build a SQL Server database directly from source control and optionally include static data
  • Fill empty tables with synthetic data
  • Integrate trigger-based audit trails and reporting into change sensitive database objects
  • Generate full or differential documentation for the SQL Server database
  • Test SQL Server database using unit tests
  • Enforce database best practices by reviewing, detecting and fixing issues
  • Create a clean database package for easy deployment
  • Publish package to a designated NuGet feed
• Continuous delivery:
  • Compare SQL Server database schemas and create a script for schema synchronization
  • Compare SQL Server static data and create a script for data synchronization
  • Push schema and data changes to a target database
• Archive all output files in a central folder
• Automatically create rollback scripts
• Flexible pipelines