You'll receive

Bi-weekly updates

Exclusive discounts

Product update alerts

 

ApexSQL Script release notes

Release:

2016.01.0258

Date:

May 10, 2016

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 support for Visual Studio 2015

Fixes:

  • The "Include dependent database objects" option is not checked by default in the Script wizard
  • Missing a dialog 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\crazy_000\Documents\ApexSQL\ApexSQLDataDiff\AdventureWorks2014.dat'" error message is encountered if the Use compression option is checked and the Create script file option is not checked
  • "Could not find file 'C:\Users\crazy_000\Documents\ApexSQL\ApexSQLDataDiff\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\'USER'\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" 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
  • Missing name for the 'Database' column in the main grid
  • Object types are not sorted in the alphabetical order in the Object filter, Main form
  • Unresponsive progress forms when connecting data source - selecting Schema mapping or Object filter
  • The quotation marks are missing in the batch script when the database name contains white spaces
  • Application help doesn't lead to Knowledgebase

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 .NET 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

Release:

2014.04.0236

Date:

September 11, 2015

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 "Script CREATE DATABASE" option is checked in the project defaults
  • When using the “Script each object into an individual file” option, the “Open script in editor” 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

Release:

2014.03.0232

Date:

March 13, 2015

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

Release:

2014.02.0231

Date:

October 13, 2014

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

Release:

2014.01.0224

Date:

July 24, 2014

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

Release:

2011.04.0218

Date:

November 28, 2013

Enhancements:

  • The application now supports Team Foundation Server 2013

Release:

2011.03.0217

Date:

September 19, 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

Release:

2011.02.0210

Date:

July 03, 2012

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

Release:

2011.01.0209

Date:

October 27, 2011

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

Release:

2008.02.0207

Date:

October 6, 2009

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

Release:

2008.01.0205

Date:

April 14, 2009

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