ApexSQL Script release notes

Fixes:

• 183811: "Parse error: Incorrect syntax near 'RANGE'" error is encountered when attempting to script the SQL database
• 183812: SQL databases are not loaded when using SQL Server 2008
• 185359: The output script doesn't include a begin transaction at the top of the script when generating individual scripts into a folder

Enhancements:

• SQL Server 2019 support
• Temporal tables support
• SQL graph tables support
• Application telemetry now collects anonymous data on the use and performance of applications and application components
• New ApexSQL Updater allows users to configure advanced updating settings of all installed ApexSQL products

Fixes:

• Empty folder structure is generated in the temporary folder and the folder is generated in the wrong location when committing scripts to the Team Foundation Server repository
• The application stops responding when scripting out filtered list of triggers from Amazon RDS database
• Applying schema or object name column filters in objects lists does not affect the list
• Data is not scripted with the Structure and data scripting mode selected when the Object filter is set after loading a database
• "Make sure correct username and password are specified" message is encountered when establishing connection to the Git repository hosted on the Azure DevOps
• Blank error dialog is shown when all the files are deleted from Team Foundation Server repository and commit is started again
• The application is not automatically closed during the update process
• Performance drop when scripting a database with 200+ users and permissions on all objects for them
• "Parse error: [Incorrect syntax near 'WITH'] at" error is encountered when the Script process is initiated with the Structure and data scripting mode and a table included has the with fill-factor value
• Database and column collation are changed, and SQL Server default collation is used when creating a database from a created executable installer
• "Method not found: 'Void DevExpress.XtraTreeLis" error is encountered when saving the project file
• Date and time are not changed for the file name in the Script wizard after one scripting process is finished and another one is started
• Filter editor under the Object filter panel in the main application window is not working
• Underscores are not added when the Date and Time tags are added for the file name under the Output tab of the Options window
• "Object reference not set to an instance of an object" error is encountered when scripting out a database to a script folder
• Missing statements to create filegroups for objects that uses them when the Filegroups option under the Structure section of the Options tab in the New project window is checked and output to script folder is selected
• Authentication type is automatically changed to the Active Directory - Universal with MFA support authentication when changing SQL Server
• Missing the Active Directory - Universal with MFA support authentication for the Connection to SQL Server dialog under the Integrated editor
• Missing source control connection parameters when generating automation script for scripting to a local Git repository
• “Repository not found: C:\Users\Username\AppData\Local\ApexSQL\ApexSQL Script\" error is encountered when scripting database to the local Git repository
• Objects are not shown in the main application window when SQL Server 2008 database is loaded
• Pre and Post processing scripts are not included in the scripting process when the Use embedded option is selected under the Additional scripts tab of the New project window
• Object type selection in the Object filter tab of the New project window is reset when any selection is made, a tab is switched and then the Object filter tab is selected again
• Database with its objects and data remains in the Structure and Data grids in the main application window, even though the project is edited, and other database is checked for loading, while the first one is unchecked
• The last used path for the automation script is not remembered
• "Object reference not set to an instance of an object" error is encountered when configuring scripting target source control parameters after second database is loaded in same application session
• Missing the option to exclude specific objects through the CLI
• Static data is not scripted for tables that do not have primary key defined

Changes:

• Dark theme is now used as the default application theme
• Save as dialogs are now inheriting the application theme

Changes:

• Software Transaction Agreement is added as a new step in the installation wizard and updated in accordance with https://www.quest.com/legal/sta.aspx

Enhancements:

• Active Directory support for:
  • Password authentication
  • Integrated authentication
  • Universal with MFA support authentication
• Visual Studio 2019 version option is added for the C# solution and Executable installer options steps in the Script wizard
• CLI switches:
  • Login for Azure Active Directory authentication [/ad]
  • New value for the Visual Studio /vs_ver switch: VS2019

Fixes:

• "ExecuteScalar requires an open and available Connection. The connection's current state is closed" error is encountered in the log file when Azure SQL Database or Amazon RDS for SQL Server is loaded, even though there is no error in the application’s GUI
• "Object reference not set to an instance of an object" error is encountered when the OK button is clicked in the Connection options dialog after changing value for timeout options
• The created C# solution is not opened upon creating it through the CLI, even though the /open_vs switch is specified
• The created executable installer is not opened upon creating it through the CLI, even though the /run_exe_now switch is specified
• The Disable all triggers and constraints prior to loading data option switch is not working in the CLI
• "Could not load file or assembly" error is encountered during the commit process to the Team Foundation Server repository
• "Index 4 is out of range" error is encountered when the Clear filter button is clicked in the Object filter panel of the main application window

Changes:

• Where clause dialog and column under the Data view are now Row filter

Fixes:

• The Extend evaluation button does not open default e-mail client when clicked and the application is opened in the Community edition
• Objects and data are scripted to the same StaticData folder when more than one database schema and data is selected for scripting
• Randomly named project are created when an existing one is deleted from the Team Foundation Server repository
• "Source control error: One or more errors occurred" error is encountered when creating new project on Team Foundation Server repository

Enhancements:

• 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

Changes:

• The application now requires Microsoft .NET framework 4.7.2
• Save as batch is now Automation script

Enhancements:

• Visual themes
• Visual Language Dictionary for Visual Studio for iconography and other imagery concepts applied
• The “Manage Owners” option is added in the New Project form
• CLI switches:
  • /on (/output_name)
  • /eso (/exclude_schema_objects)

Fixes:

• The Windows taskbar is not shown on mouse hover when the Auto-hide the taskbar option is checked and the application is maximized
• The ''Row filter'' option is missing under the Structure view
• The executable installer does not check if there is a previous version installed
• The Run executable installer now option is unchecked when the Back button is clicked in the Export batch form
• When adding pattern in the Object filter step of the wizard pattern should become active when checked
• “loading objects failed” error is encountered if no database is selected when initiating Schema mapping or Object filter
• Unresponsive progress forms when connecting data source selecting Schema mapping or Object Folder
• The Create database option cannot be saved as "my defaults" in the connection form under the structure tab
• Missing a prompt dialog whether to uninstall the previous version or cancel the current installation
• Parsing errors keep reoccurring once encountered
• “Automatic updates” options are not checked by the default in the application
• Indicator of excluded objects doesn't respond in the status bar under Data tab
• Indicator of excluded objects doesn't respond in the status bar under Structure tab
• Lack of summary after scripting process
• Missing the Logging option in the Package tab
• The Working folder is redundant as a source control system
• Missing line numbers in the Where clause window
• Unable to execute file in temporary directory Setup is aborted when downloading and installing the application
• "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 TFS
• Objects still showing for scripting even if they were deselected in the Object filter
• Compatibility level option is not saved in the project
• "Parse error: [Incorrect syntax near 'READ']" error is encountered while parsing the procedure
• Missing the /exclude_dependent_objects switch that will exclude objects that depend on the excluded objects specified in the /exclude
• The license file disappears when virtual machine is stopped and then run on Amazon AWS
• "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
• Wrong CLI switch is used for the output name in the Save as batch window when SQL script is selected as the output type
• Arguments can be combined in output_elements switch error is encountered while exporting the CLI help file into HTML
• Wrong switches and values are generated and missing switches in the Save as batch window when the solution is selected as the output type:
  • C#
  • Executable installer
  • Script folder
  • Source control
• The application stops working when the Commit button is clicked with Source control as the Output type without providing source control credentials
• The Create database option cannot be saved as "my defaults" in the connection form the structure tab
• When using dual setup monitor environment application starts on the secondary monitor regardless if it was used on the primary

Changes:

• The application now requires Microsoft .NET framework 4.7.1
• Windows Vista and Windows Server 2008 are no longer supported
• The /pf switch is changed to /pr CLI switch
• Removed /fl, /in, /fn, /sta, /stc, /stl, /stc1, /stc2 and /stc3 CLI switches

Enhancements:

• 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

Enhancements:

• SQL Server 2016 support
• Azure SQL Database V12 “full” support (all new features)
• Save project as a batch file option is added as a step in the scripting wizard
• New /filename (/fn) switch has been added to CLI to specify the name of the scripted file
• New /sourcecontrol_depot (/scdep) switch has been added to CLI to specify the depot for the Perforce source control system
• New /sourcecontrol_workspace (/scwrsp) switch has been added to CLI to specify the workspace for the Perforce source control system
• New /db_compatibility_level (/dbcl) switch has been added to CLI to set the desired compatibility of the extracted files with the specific SQL Server version
• New /sourcecontrol_branch (/scbr) switch has been added in CLI for specifying a branch in Git repository
• Check-box is added for selecting a whole type of objects in the Main grid
• Execution results has been added to Executable installer
• The group of options is added in the Project defaults for setting the compatibility mode of the scripted database
• C# solution and executable installer support for Visual Studio 2015

Fixes:

• The Include dependent database objects option is not checked by default in the Script wizard
• Missing a prompt window to confirm whether to use .dat file when running the executable installer
• The Run executable now option is checked by default, in the scripting wizard
• "Package executed successfully" message is always encountered, even if something went wrong during the execution of the Executable installer
• The application closes when the Save as button is clicked in the Internal editor
• "Could not find file 'C:\Users\UserName\Documents\ApexSQL\ApexSQLScript\AdventureWorks2014.dat'" error message is encountered if the Use compression option is checked and the Create script file option is not checked
• "Source control error: Could not find a part of the path 'C:\Users\UserName\AppData\Local\Temp\ApexSQLScript..." error message is encountered while committing files to Team Foundation Server project
• "There was an error when processing files. The directory is not empty" error is encountered while committing scripts to Subversion source control project
• Missing a step in the installer that will check if there is a previous version installed and to remove it
• "Incorrect syntax" error message is encountered in the Where clause filtering when the object/schema is named as a T-SQL keyword
• Extended properties are not scripted for clustered index
• Table columns are not checked on Check all in the column header of the main grid
• Insert statements are not scripted when the alter database name option is checked
• The Object filter does not apply to the project when it is set from the connection form
• The Developer edition should be changed to the Standard edition in the "About" form
• The Optional package information are not saved after being set up in the Defaults from>Package tab
• The source control folder is created in the wrong location - C:\Users\UserName\AppData\Local\Temp\ApexSQLScript2014
• "Source control path is not specified" error is encountered when running the CLI command to script objects/data
• "Source control working folder is not specified" error is encountered when omitting the switch for the working folder
• The application will script all objects instead of just changes ones when specifying the CLI command
• "Connection failed with message 'Invalid remote:origin" error is encountered when committing objects on a Git repository
• When the CLI is used, there is no way to supply timestamp for the source control comment
• The options configuration set in the connection form is not being synchronized with the options in the Defaults form once the project has started
• Object types are not sorted in the alphabetical order in the Object filter, Main form
• Unresponsive progress is encountered when the Schema mapping or Object filter tabs are selected while connecting to data source
• The quotation marks are missing in the batch script when the database name contains white spaces

Changes:

• The Additional scripts tab are only available in the Professional edition
• The Package tab is only available in the Professional edition
• The term “Version” is changed to “Edition”
• Create C# solution from SQL database is available only in the Professional edition
• Create SQL database executable installer is available only in the Professional edition
• Tag brackets has been replaced with the "%" character

Enhancements:

• Full support for Perforce source control system
• Full support for Mercurial source control system

Fixes:

• The application is scripting an incomplete script, when the output file encoding is set to UTF7 or UTF8
• The “Object filter” options are not reloaded correctly, when a custom filter is chosen
• Great delay in selecting objects, in the “Object filter” pane, when a database has more than 100.000 objects
• Some objects will be selected when loading a custom object filter
• Local SQL Server instances are not shown in The "Local servers" list
• The "Script drops" option does not script schema objects with the IF condition
• The drop-down list in the "Filter editor" feature disappears when the filter is entered, the OK button is clicked, and then re-entered again
• Two project windows will open, after the application is updated, and a recent project is loaded
• Missing the file path information after executing the “/output_type” and the “/folder” switches in the CLI
• The application window cannot be displayed on screen when using a multi-monitor setup
• “Database is not specified” message is encountered when the project file is loaded in the CLI
• The application will script all objects in the CLI, even if only one object is selected for scripting in the project file
• After closing the resized application window, it's not remembered on the next start up
• The application creates additional files, when scripting database as an executable installer
• The application does not have "any CPU" configuration
• The Script editor window will be opened, if any column name is clicked in the Main window
• The Name filter cell, in the Object filter tab, is not working
• The application does not use the one save folder for all databases, if C# solution or executable installer is selected as an output source
• The version number is not inserted correctly when the Script each object into an individual file option is selected
• Cannot alter the database name in the Output file options windows, even if the Create database option is checked under the Script tab in the project defaults
• When using the Script each object into an individual fil” option, the Open script in edito” option functions the same as the Save scripts to file(s) option
• “Object reference not set to an instance of an object” error message is encountered when running only the connection switches in the CLI
• The packaging option is not working from the CLI if the data mode is used
• The /package_comments CLI switch has no function
• Missing a switch for the Alter database name in the CLI
• Missing switches for the Output file options under the C# solution
• Missing switches for the Output file options under the executable installer
• “’ApexSql.Package.PackageOptions' does not contain a definition for 'IsDatabasePropertiesVisible'” error is encountered when C# solution and executable installer is created with data mode and then run in Visual Studio

Changes:

• The application now requires Microsoft .NET framework 4.5
• Windows Server 2003 is no longer supported
• Support for SourceGear Vault source control system has been deprecated
• Support for Microsoft Visual SourceSafe source control system has been deprecated
• Support for MSSCCI-compliant source control systems have been deprecated

Enhancements:

• The application now supports Azure SQL Database V12
• The "Alter database name" option is added

Fixes:

• The "Extended property editor" feature is not available in the Community edition
• A parse error is encountered while scripting a specific stored procedure
• A parse error is encountered while scripting a specific schema
• A parse error is encountered while scripting a drop index procedure
• The database becomes unchecked when one or more dependent objects are unchecked
• The "?" button from the Extended property editor window is not leading to appropriate page

Enhancements:

• The application now fully supports SQL Server Express Edition
• The application now fully supports SQL Azure
• The application now fully supports SourceGear Vault up to version 6.1

Fixes:

• Missing information that the "/o" and "/include" switches cannot be used together
• The "Not found. Sorry, but we couldn't find the page you were looking for" error is encountered when the F1 button is pressed
• The "The path is not of a legal form" error is encountered when the "Scripting wizard" is started for SQL Azure
• The value for a file name is inputted on cursor position in the "Output file" options
• The "Save scripts to file(s)” location is reset when changing the "Output action" options
• The IDENTITY feature in table columns is ignored when scripting table with "xxx.yyy" SCHEMA format
• The server used in the last session is not remembered in the "New project" window
• Only the first page is shown in the "Print preview" option
• The "Script header" form can be multiple divided
• The "New project" window is not resizable
• All tables that are checked become unchecked when the "Edit SQL WHERE clause" option is used
• The created script cannot be opened when SQL Server 2014 Management Studio is selected as an editor in the "Script wizard"
• The "Parse error: Internal parser error." error is encountered when the CANCEL button is clicked, while including dependent database objects
• The main grid is not auto filled with columns to cover the white space in the "Data" and in the "Structure" views
• The "OK" button in the "Edit max value" dialog does not work
• The "OK" button in the "Edit object alias" dialog does not work
• The "Uncheck fields" option causes incorrect checking/unchecking objects from the "Data" view
• Missing the "Select Visual studio version" option in the "Output file options" when creating C# project
• The "Parse error: incorrect syntax near 'next' at position [x,y] in query [xxyy]" error is encountered when scripting specific stored procedure
• Data types datetime2 and datetimeoffset are scripted incorrectly as data types binary(8) and binary(10)
• The "Parse error: Error : [Incorrect syntax near 'DBCC']" error is encountered when scripting a DBCC statement
• The "Red X" error is encountered when loading objects from a database which contains more then 5,000 objects
• The application is non-responsive when scrolling through a large number of objects in the main grid
• The application is unresponsive when more than 100,000 objects are selected for scripting

Changes:

• The application has been split into three editions - Community, Standard and Professional

Known issues:

• Local server result panel says that "No servers detected" although local instance exists when the application is used on 64bit operating system with 64bit SQL Server

Enhancements:

• The application now fully supports SQL Server 2014
• The application now fully supports Apache Subversion up to version 1.8.9
• The application now fully supports Git up to version 1.9.4

Fixes:

• The Script wizard can be opened without any object checked for scripting
• Docking the “Object Filter” pane to the center area removes it from the GUI without an option to reverse action
• The application is generating different scripts after saving files in two different locations
• The "Could not load file or assembly" error is encountered when connecting to Team Foundation Server 2013 and Team Foundation Server 2010

Changes:

• New user interface that follows Metro UI style

Enhancements:

• The application now supports Team Foundation Server 2013

Enhancements:

• The application is now FIPS compliant

Fixes:

• If checked when saving the project file, the pre-processing feature's "Use this Script" option will remain unchecked in the saved project file
• When dependent SQL views is scripted, the child SQL view is wrongly scripted before its parent SQL view
• Cancelling the script wizard (or/and) opening results in termination only if initiated in early stage
• SQL object's extended properties are not scripted
• The extended property editor doesn't match the color scheme of the application GUI
• The "FileTable objects require the FILESTREAM database option DIRECTORY_NAME to be non-NULL. To create a FileTable in the database 'FileTablesDB', set the DIRECTORY_NAME option to a non-NULL value using ALTER DATABASE. Or, to set the DIRECTORY_NAME option to NULL, in the database 'FileTablesDB' disable or drop the existing FileTables." error is encountered when executing script created for the database with SQL Filestream data
• The "INSERT statement failed because data cannot be updated in a table with a columnstore index. Consider disabling the columnstore index before issuing the INSERT statement, then rebuilding the columnstore index after INSERT is complete." error is encountered when executing script created for SQL database with columnstore indexes
• Dependent SQL database objects are not scripted when using the CLI for scripting SQL database
• Project default options button have no effect on the current project, and it can be applied after creating a new project or restarting the application
• The "CREATE FULLTEXT STOPLISTS statement cannot be used inside a user transaction" error is encountered when executing created SQL database script
• The "CREATE SEARCH PROPERTY LIST statement cannot be used inside a user transaction." error is encountered when executing created SQL database if Document property list option is selected during creation
• The application doesn't detect SQL triggers as table dependent objects which results in ENABLE and DISABLE triggers constructions to be included in the resulting script, without CREATE TRIGGER constructions
• The application wrongly generates creation script for non-clustered index with the DESC keyword after the INCLUDE clause
• Missing tooltips for all buttons in the Ribbon bar
• The unwanted Expand Groups effect occurs each time when switching between 'Structure' and 'Data' tabs
• Scripting Wizard closes in Structure mode when Data Scripting is initiated without selected object
• Advancing through Structure scripting Wizard is allowed even if at least one object is not selected
• Application wrongly adds an extra column as a key when scripting a database with non-clustered index in a partitioned table
• The "Invalid bitwise set" error is reported when bitwise set constant for more than one object is used in the CLI
• The regular expression "^" does not match its starting position within string when used in the CLI
• Multiple object types cannot be used with /exclude the CLI switch
• Explicit permissions on SQL schemas are not scripted even the "Script permissions" option has been selected
• The application stops working when the 'Include dependent database objects' option is checked

Changes:

• The "/no_scr_ex_properties" CLI switch has been renamed to "/scr_ex_properties", and it enables SQL object's extended properties to be scripted via the CLI

Enhancements:

• The following SQL Server 2012 object types are now fully supported:
  • Sequence
  • Search property list
• 'SQL Server 2012 Management Studio' output editor setting has been added to the Options form to allow opening the synchronization script in SQL Server 2012 Management Studio

Fixes:

• Data grid doesn't have filter conditions dropdown button menu in the right corner of the Name column filter cell
• 'Microsoft.VC80.CRT' unneeded folder is created during installation in the application installation folder
• Project Settings dialog Object filter step Common Object Types checkboxes are horizontally misaligned
• Main grid object filter grouping is not preserved between application sessions
• Connection options in Select databases step of Project Settings dialog can be modified while database list is updated
• Two online help documentation pages are opened when F1 keyboard shortcut is used to request help in Extend property editor

Enhancements:

• SQL Server Denali CTP3 databases can now be scripted including the following new features:
  • Search property list name attribute for Fulltext Indexes
  • Poison message handling attribute for Queues
  • Geometry and Geography Auto Grid tessellation scheme for Spatial Indexes
  • File Tables
  • Column Store indexes
• Fulltext Stoplists are now fully supported
• SQL Server 2005 and higher version encrypted objects can now be scripted (requires membership in the sysadmin server role)
• Extended property editor has been implemented in the application
• Progress dialogs have been redesigned across the application for improved accuracy and usability
• New Office 2007 style interface with ribbon bar, quick access toolbar, and ApexSQL Script button
• New Resources ribbon bar is introduced for quick access to Help page, Support forum, Training page, FAQs, Knowledge base, Troubleshooting, About and Get Updates dialog boxes
• Options dialog box has been redesigned with new Office 2007 button bar
• Project Defaults can now be defined for newly created projects
• Project options can now be saved as current user defaults settings
• Project options can now be reset either to current user or to ApexSQL defaults
• Tooltips with option description are shown for Project options
• Project Management dialog box now shows recently used projects or projects saved in any folder of choice
• Projects can be Pinned/Un-Pined to Recent Projects list on Project Management dialog box
• Projects can be opened directly from Project Management dialog box
• Project description can be edited directly from Project Management dialog box
• 'Show on Startup' option has been added to Project Management dialog box
• Output type and Scripting mode are shown directly in Project Management dialog box for selected project
• Show Advanced Tabs button in Project Management dialog box displays additional steps (Script Formatting, Package, Schema Mapping, Object Filter and Additional Scripts)
• Dependent objects can now be viewed and selected for scripting individually on Dependencies step of Script wizard
• Script editor can now be selected on Output Options step of Script wizard
• Results grid supports 3 predefined grouping types: Group by database, Group by object type and Group by both database and object type
• New Object Filter that allows setting filter both for particular object type and for all types has been introduced for Structure grid
• Object Filter allows defining filtering criteria using Filter Editor
• Filter Editor allows to interactively create filtering expressions using Name and Schema fields
• Filter Editor allows to filter script objects based on 'Exclude if' or 'Include if' conditions
• Filter Editor criteria can use the following comparison operators: 'Equal', 'Not Equal', 'Between', 'Not between', 'Contains', 'Not contains', 'Begins with', 'Ends with', 'Any of' and 'None of' and the following logical operators: 'And', 'And not', 'Or' and 'Or not'
• Object Filter settings can be exported to or imported from a file
• Object Filter items can be grouped by SQL Object Type or by Category
• Number of selected objects and number of filtered objects are now displayed in main window status bar
• Startup action ('Show Project Management dialog', 'Show last opened project' and 'None') can now be set in Options dialog box
• Application can now be presented in 3 color schemes: Blue, Silver and Black
• Script wizard now indicates numbers of databases and objects selected for scripting
• Output options have been redesigned for improved usability

Fixes:

• System databases cannot be selected in CLI
• Application adds an extra column to the key when scripting non-clustered indexes on partitioned tables
• "Object reference not set to an instance of an object" error is encountered when saving an existing project opened with the use of Windows extension handling
• No settings is restored from an existing project opened with the use of Windows extension handling
• "Object reference not set to an instance of an object" error is encountered when executing generated .NET package on a machine with no SQL Server installed
• Dbo schema isn't displayed in main grid and cannot be scripted
• Custom extensions are not applied when scripting to individual files
• "System.IO.PathTooLongException" exception is encountered when saving generated C# solution with too long name
• View data is scripted by default with /mode:both specified in CLI
• Same alias can be assigned to more than one table in data mode
• 'The application's folder is read-only' error is encountered on application startup if application folder is read-only
• Partition Function parameters of nchar and nvarchar data types get scripted with incorrect length
• Extended properties get scripted in different order depending on SQL Server version
• Schema bound Functions and their dependencies get ordered incorrectly in generated scripts
• Functions don't get identified as dependencies when referenced in DECLARE statements
• Different warnings are displayed when setting the same working folder for different projects depending on Native Source Control driver used
• Xml values containing Unicode characters get scripted incorrectly
• Aliases are not applied to ALTER TABLE, comments and PRINT statements in data mode
• Individual Object Scripting Results dialog is not shown when scripting to Source Control
• Paths to database files vs folders are offered as default settings for Database and Log Directory options of .NET package
• Real values may be scripted with precision loss depending on its length
• Binary values stored in sql_variant data type get scripted incorrectly
• Date and time values may be formatted incorrectly in generated scripts
• Decimal/numeric and binary values of maximal allowed length are not scripted
• Text values containing Unicode characters get scripted incorrectly

Changes:

• Switching between Data and Structure grids in main window are now done through tabs
• Regular Help button has been replaced with question mark button in title bar on all dialogs and windows
• The following options have been moved to Project Setting form Script wizard
  • Schema Mapping
  • Common
  • Script Processing
  • Structure scripting
  • Data scripting
  • Script formatting

Enhancements:

• Application is now able to script to the following Source Control systems via the ApexSQL Source Control add-in:
  • Subversion
  • Team Foundation Server
  • SourceGear Vault
  • Microsoft Visual SourceSafe
• Scripting to Source Control systems is now done via Source Control wizard
• New Folder Mapping tab was added to Options form
• Object type folders can now be configured separately when scripting to folder
• Objects are now shown grouped by database in main grid
• Databases can now be scripted to separate files via 'Create separate file for each database' option in single file mode
• The following new object types are now supported:
  • Event Notifications
  • Remote Service Bindings
  • Aggregates
  • CLR Functions
  • CLR Procedures
  • CLR Triggers
• It's now possible to add comments to and label scripted files when scripting to Source Control systems via the ApexSQL Source Control add-in

Fixes:

• Check constraints are scripted with extra line break before GO
• Script "Use for Database" and "Script Update Statements" options have the same hotkeys in Script Wizard
• Connect button is always enabled in Project Wizard
• Manage Project, Project Properties, Add SQL Server, and View DDL forms point to non-existing help pages
• FILESTREAM filegroups are incorrectly scripted in CREATE DATABASE statements
• Filename templates aren't validated in Script Wizard

Changes:

• When generated script can't be opened with internal editor (when it's >3MB in size), user is offered to save the script and open it in another editor
• All selected objects from all selected databases are now shown in main grid when Project Wizard closes
• Database Explorer panel has been removed
• Script Wizard's Source Control Settings step has been removed
• Mutiple file mode's Filename Template option has been removed
• {extension} object tag has been removed
• Extension column in Object Tags tab (under Options) has been removed
• The following new switches have been added to CLI:
  • /sourcecontrol_type - specifies supported Source Control type (microsoftvisualsourcesafe, subversion, sourcegearvault, teamfoundationserver)
  • /sourcecontrol_server - specifies server
  • /sourcecontrol_user - specifies user
  • /sourcecontrol_password - specifies user password (used with /sourcecontrol_user switch)
  • /sourcecontrol_project - specifies project
  • /sourcecontrol_repository - specifies repository
  • /sourcecontrol_working_folder - specifies working folder
  • /create_file - creates separate file for each database in single file mode
  • /folder_mapping - specifies folder mapping file (default mappings if omitted)
• The following CLI switches have been removed:
  • /create_dir
  • /source_safe
  • /vss_config
  • /vss_user
  • /vss_password
  • /vss_project
  • /vault
  • /vault_server
  • /vault_repository
  • /vault_user
  • /vault_password
  • /vault_project
  • /output_file
• Application roles are now treated as regular database roles everywhere in application

Enhancements:

• Support for SQL Server 2008 table-valued user-defined types
• Support for SQL Server 2008 SPARSE columns
• Support for SQL Server 2008 FILE_STREAM columns
• Support for SQL Server 2008 DATA_COMPRESSION option
• Support for SQL Server 2008 READONLY parameters of SQL Server 2008 procedures
• Support for SQL Server 2008 Geometry, Geography, HierarchyID, Time, Date, Datetime2, Datetimeoffset types
• Support for SQL Server 2008 XML_COLUMN_SET columns
• Support for SQL Server 2008 CRYPTOGRAPHIC_PROVIDER credential attribute
• New "Manage Projects" form instead of Project step of Project Wizard
• Added "Script USE for Database" option to "General" page in "Data Only" mode

Changes:

• Offline help file is no longer provided and application will now directly access online help from the default system browser
• Default Folder for projects is changed to be \My Documents\ApexSQL\ApexSQLScript2008 instead of \My Documents\ApexSQL\ApexSQLScript
• Main toolbar divided into two toolbars: main toolbar with general actions and grid toolbar (hidden by default) with buttons for main grid manipulation
• Removed "Explicitly Parse Database for Proper Script Creation Order" option from Script Wizard