ApexSQL Script Professional 2018.02

Adds support for SQL Server 2019 CTP 2.0.

Features

• Microsoft SQL Server 2019 CTP 2.0 support.
• High DPI and 4K resolution support.
• Save automation script as a PowerShell script.
• New error handling and send logs functionality.
• Improved application installer with a dark theme.
• New application icon.
• Check for object existence with If exists/If not exists option is added under the Options tab of the New project window.
• Include dependent database objects option is added under the Options tab of the New project window.
• CLI switches:
  • Name of the executable installer or C# solution package [/pknm].
  • Output name/folder path of the SQL script, script folder or executable packages [/on].

Fixes

• "Source control error: Comment cannot be empty" error is encountered while creating new project for Mercurial source control without entering a comment
• "There was an error when processing files. The directory is not empty" error message is encountered when committing to Subversion and Git project label
• "The path is not of a legal form" error is encountered when running executable installer if it was created with the Use compression option and saved in the ApexSQL Script installation folder
• "Source control project path is not specified" error is encountered when running the CLI to commit objects/data without the /scj switch for setting up the source control project
• "Source control working folder is not specified" error is encountered when omitting the switch for the working folder
• Executable installer cannot execute a script to create a database on Azure SQL Database V12
• "Failed to commit operation with message 'No pending changes'" error is encountered when creating a subproject on Team Foundation Server repository
• Triggers are not being disabled or re-enabled when scripting only data
• "Parse error: Incorrect syntax near '@SB'" is encountered when scripting a stored procedure that contains uniqueidentifier
• Creating of new projects from the Source control wizard for the latest version of Mercurial source control system 3.9 and above is not working
• Labels are applied to each commit to source control repository, even when label is not provided in the Output file window
• "Please check the 'Script create database' option in project defaults" message is shown when the Use for database option is checked in the Options tab and the Alter database name is checked in the SQL script options step of the Script wizard
• "NGit.Errors.TransportException: https://UserName@bitbucket.org/UserName/citest.git: not authorized" error is encountered while committing objects to Git repository from the CLI
• "Login failed for user 'sa'" error is encountered when /user and /password switches are used in the CLI to override settings in the project file
• "Switch '/scusr (/sourcecontrol_user)' can only be used with a switch '/sctype (/sourcecontrol_type)'" error is encountered when the /scusr and /scpwd switches are specified with the /project switch
• The application commits data for tables to the source control repository that were only checked in the Structure view
• "Could not load file or assembly 'Newtonsoft.Json, Version=7.0.0.0...' or one of its dependencies. The system cannot find the file specified" error is encountered when the Test or Finish button is clicked once all system logins are provided for Team Foundation Server repository
• The Branch option is wrongly loaded as the /csbr switch in the Save as batch window
• The Create database option is wrongly loaded as the /scr_create_d switch in the Save as batch window
• Objects are showed for scripting, even if they were deselected in the Object filter tab after editing the current project
• Incorrect CLI switches are created for the Disable all triggers and constraints and Apply date format options in the Save as batch window
• CLI switch /owner_type is showed twice in the Save as batch window
• "Bad format of switch: /owner_map" error is encountered in the CLI after loading the created batch script that contains the Owner mapping option
• Switches /no_transaction_handling and /no_format_scr_header are created in the Save as batch window, but cannot be used when the output type is C# solution or Executable installer
• "Bad format of switch: /db_size" error is encountered in the CLI after loading the created batch script that contains the database size option
• "Bad format of switch: /package_author" error is encountered in the CLI after loading the created batch script that contains the Author option for the Optional package information
• Missing the back-slash (/) before the /owner_type switch in the Save as batch window
• "Source control error: Cannot checkin pending changes 'The array must contain at least one element'" error is encountered while committing a database to a Team Foundation Server repository
• "Could not load file or assembly" error is encountered when the Browse button is clicked to select a project for a Git repository hosted by Visual Studio Online
• The /exclude switch is not working when specific object type needs to be excluded
• The excluded schema is not shown in the script even though it was shown and checked in the Include dependent database objects step of the Scripting wizard
• "Could not load file or assembly " error is encountered when the Browse button is clicked to choose project for all source control systems
• "Database is not specified" message is shown in the CLI when exporting CLI help file to HTML
• Wrong alias is used for the project file switch in the CLI
• Missing output types and wrong naming of the existing ones in the CLI
• Missing and wrongly named compatibility levels for the /db_compatibility_level CLI switch
• Missing and wrongly named Visual Studio versions for the /vs_ver CLI switch
• When trying to open a project from the Recent projects option in the New project window nothing happens, even though there is recent project created and present
• Object filter is not filtering the selected objects once the Load button is clicked
• The Setup button in the Source control options of the Script wizard is not working after closing and re-opening the Source control wizard
• The application stops working when the X button is clicked in the main application window after editing the project options
• The application can be uninstalled even when it's running
• The Row filter not shown for the Structure view and its button is under the wrong group in the View tab
• Missing the Default collation and SQL Server version options under the Source control options step of the Script wizard
• Pre and post processing scripts cannot be set both at once
• "Could not load file or assembly 'SharpSvn" error is encountered when the Browse button is clicked to select project for the Subversion source control repository
• Static data is not committed to source control repository when any source control system is used
• "The version of the selected solution is higher than the solution version supported by this Visual Studio release" message is shown when Visual Studio 2017 version is selected in C# solution options in the Script wizard and the created solution is opened
• Object header and Pre-script options are loaded and checked by default in the Save as batch window even though these were not set in the project
• "Arguments can be combined in output_elements switch" error is encountered while exporting the CLI help file into HTML
• Wrong CLI switch is used for the output name in the Save as batch window when SQL script is selected as the output type
• Wrong switches are generated and missing switches in the Save as batch window when the Script folder is selected as the output type
• Wrong switches are generated and missing switches in the Save as batch window when the Source control is selected as the output type
• Wrong switches and values are generated and missing switches in the Save as batch window when the C# solution is selected as the output type
• Wrong switches and values are generated and missing switches in the Save as batch window when the Executable installer is selected as the output type
• "The server was not found or was not accessible" error is encountered in continuous loop when loading the project file with saved connection that does not exist any more
• "Enter username and password" message is shown when a project file from the previous major version is loaded that contains saved user name and password for SQL Server authentication
• Structure and data options under the Options tab of the New project window are not saved in the project file and therefore default options are loaded along with the loaded project file
• Previously saved SQL Server credentials in the project file are not loaded along with the project file
• The Save as my defaults button doesn't saves custom options under the Options and Package tabs in the New project window
• Wrong project name is loaded in the Batch script panel when the project file is saved in the Save as batch window
• Wrong default project name is shown when the Save button for the project file is clicked in the Save as batch window
• Project file with a wrong name is saved along with the created batch file
• "File doesn't exist or is of incorrect format" error is encountered when the saved project file is run through the CLI
• "Cannot connect to 'Server.Name'. The target principal name is incorrect" error is encountered when the previously saved project file with Azure SQL Database connection credentials is opened and the Connect button is clicked
• The Save as batch window is closed when the Cancel button is clicked in the Save as window
• Default settings are not correctly checked for the Apply date format under Options tab in the New project window after the application installation
• "Branch name is not allowed" error is encountered while committing objects to a source control repository via the CLI
• SQL output script is created with no data rows when the Where clause option is used to filter rows
• Static data is not committed to a source control repository through the GUI
• Package and Additional tabs, along with Script folder, Source control, C# solution and Executable installer output types are not available in the Evaluation period
• The /output_name switch is missing in the Batch script panel when executable installer or C# solution are selected as output type
• The Date and Time tags are not formatted correctly in the Save as batch window for the /package_name switch
• Wrong branch name is set for the /scb switch when Git source control repository is set in the Save as batch window
• Redundant /scf CLI switch is loaded in the Batch script panel when source control is selected as the output type
• Missing quotation marks for the /scr and /scj switches in the Save as batch window when source control is selected as the output type
• Missing value for the /scr switch and missing /scj switch in the Save as batch window when Perforce source control information are loaded
• "Connecting to source control server [localhost:1666] has failed Authentication was failed with message 'ProjectName is a depot, not a client" error is encountered while committing to the Perforce source control repository from the CLI
• "The specified folder does not contain the appropriate folder structure" message is shown when a selected source control project contains the Assemblies folder
• The Include dependent objects step is not shown when the Structure and data scripting mode is selected in the Script wizard
• "Windows logins are not supported in this version of SQL Server" error is encountered when trying to save a Where clause while connected to Azure SQL Database
• "The login is from an untrusted domain and cannot be used with Integrated authentication" error is encountered when trying to save a Where clause while connected to Amazon RDS for SQL Server
• The Compatibility level option is not working in the GUI
• The /db_compatibility_level switch is not working when run in the CLI
• The application now requires Microsoft .NET framework 4.7.2
• Save as batch is now Automation script