Adds support for Microsoft SQL Server 2017 and Amazon RDS for SQL Server.
Features
- Microsoft SQL Server 2017 support.
- Amazon RDS for SQL Server support.
- Exclude all objects with schema name specified in the /exclude switch [/eso].
Fixes
- "Cannot insert duplicate key in object 'SchemaName.TableName'. The duplicate key value is (0)" error is encountered when executing the generated SQL script to create a trigger after renaming a table and creating a view on which trigger depends on.
- The application repeatedly asks for the activation key when it is started on an Amazon EC2 instance after the virtual machine resources were deallocated and allocated again.
- The /exclude switch is not excluding a specified object type.
- "Parse error: [Incorrect syntac near 'READ']" error is encountered while defining a clustered primary key in the create table statement that contains specification of a file group for a clustered primary key.
- "Parse error: [Incorrect syntax near ')']" error is encountered when the Script button is clicked for a database that has a compatability level 140.
- "Parse error: [Incorrect syntax near 'trén']" error is encountered when scripting procedure with French characters.
- Ansi options are missing from the beginning of the created script when the script header is unchecked.
- Not all object types are shown in the Mapping configuration window for the SQL Server 2012 databases.
- "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.
- "Could not find a part of the path 'C:\Users\UserName\AppData\Local\ApexSQL\ApexSQLScript\Options.xml'" error is encountered upon closing the application when previoulsy the complete Script wizard was canceled in the last step of the Source control wizard.
- The Branch option in the Source control wizard only shows the Master branch, even when other branches are created.
- Back slashes are repleaced with forward slashes when setting up the local repository path for Git and Mercurial in order to disable the Username and Password information.
- Username and password are not greyed out for the local Mercurial repository and it always requires at least something to be entered for the Username and Password fields.
- The created source control project committed by the application stops working when any other ApexSQL tool tries to connect to it.
- "Switch 'data_disable_constrains' is not recognized" message is shown in the CLI when the batch script is run and it was previoulsy created from the application GUI where the Disable all triggers and constraints option was checked.
- "StartIndex cannot be less than a zero" error occurs when running the Batch script in the CLI that was previoulsy created from the application GUI where the Create and commit to source control action was selected.
- Non existing folder is added in the Batch script for the location of the /script_header and /folder_mapping CLI switches.
- Obsolete CLI switches for source control information are shown in the Batch script.
- The database compatability level option from the Structure tab in the New project window is not saved in the project file.