Includes updates to ApexSQL Doc, Generate, Script and Unit Test.
Features
- New in ApexSQL Doc 2018.02
- Performance has been improved for generating documentation with graphical dependencies up to 350%.
- New in ApexSQL Generate 2018.01
- High DPI and 4K resolution support.
- Applied concepts of Visual Language Dictionary for Microsoft Visual Studio for iconography, imagery, colors, menus, fonts, formatting and other GUI elements.
- CLI there are no empty tables in database return code [104].
- CLI switches:
- Output elements [/oe].
- Loop [/lp].
- New in ApexSQL Script 2018.01
- Visual themes.
- Visual Language Dictionary for Microsoft Visual Studio for iconography and other imagery concepts applied.
- "Manage Owners" option is added in New Project form.
- Added /on (/output_name) and /eso (/exclude_schema_objects) CLI switches.
- New in ApexSQL Unit Test 2018.01
- High DPI and 4K resolution support.
- Applied concepts of Visual Language Dictionary for Visual Studio for iconography, imagery, colors, menus, fonts, formatting and other GUI elements.
Fixes
- Fixes in ApexSQL Analyze 2018.02
- "Loading object and dependencies failed" error is encountered when the Connect button is clicked in the Connect to SQL Server window for SQL Server 2017 version: 14.0.1000.169.
- "Loading object and dependencies failed" error is encountered when the Connect button is clicked in the Connect to SQL Server window to connect to the AdventureWorks2016CTP3 database.
- Clicking the Help button in the Resources tab leads to a missing web page.
- "Object reference is not set to an instance of an object" error message is shown when analyzing a database that contains a syntax error.
- "Object reference not set to an instance of an object" error is encountered when selecting an object and clicking the "Show script" button.
- The silent installation is stopped when the application needs to automatically download and install .NET Framework, even when the /verysilent switch is used.
- 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.
- Fixes in ApexSQL Data Diff 2018.04
- "Could not load file or assembly 'Windows-Drive:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\ApexSQL.Engine.Controller'" error is encountered when a backup is loaded as a data source in the Data sources tab of the New project window.
- "Unknown error has occurred. Please see %AppData%\Local\ApexSQL\ApexSQL AppName>\crash.txt" error is encountered when ApexSQL Log or ApexSQL Recover are started while ApexSQL Data Diff is installed.
- Fixes in ApexSQL Diff 2018.02
- "The Community edition can connect only SQL Server Express, Azure SQL Database and Amazon RDS for SQL Server" message is shown upon start of the comparison process, even though the entered credentials are for connecting to Azure SQL Database.
- "The Community edition can connect only SQL Server Express, Azure SQL Database and Amazon RDS for SQL Server" message is shown upon start of the comparison process, even though the entered credentials are for connecting to Amazon RDS for SQL Server database.
- "The Community edition can connect only SQL Server Express, Azure SQL Database and Amazon RDS for SQL Server" message is shown upon start of the comparison process, even though snapshots were selected for the comparison.
- "The Select permission was denied on the object 'sql_logins', database 'master', schema 'sys'" error is encountered during the comparison of Azure SQL Database.
- The saved Object filter settings are not applied when loaded in the Object filter panel in the main application window.
- The Object filter panel settings are not applied when the data sources of the current project are edited.
- "Parsing errors: Parse error: [Incorrect syntax near 'NOEXPAND'] at [position: 857, line: 22, column: 34]" error is encountered while comparing database with script folder which contains the script with Noexpand in it.
- "Parsing errors: Parse error: [Incorrect syntax near 'tv_products'] at [position: 8795, line: 150, column: 32]" error is encountered while comparing a source control project with a database that contain a procedure with the With (nolock) statement.
- Fixes in ApexSQL Doc 2018.02
- "Failed to run hh.exe" error message is encountered when generating database documentation in docx file format.
- "Dependency Explorer Console has stopped working" error message is encountered when generating documentation with graphical dependencies.
- Application stops responding when adding SSIS or SSRS package from file system.
- Empty documentation is generated when documenting Visual Studio 2017 SSIS packages.
- Application stops responding when generating documentation for multiple databases in HTML file format.
- Application stops progress at 51% when generating documentation with graphical dependencies.
- Fixes in ApexSQL Enforce 2018.03
- "Do you want to install .NET Framework 4.7.1" message is shown when installing the app via CLI using /VERYSILENT and /SUPPRESSMSGBOXES switches.
- The Rule column filter in the Resultset grid does not show filtered objects.
- "Unexpected error occurred." error is encountered when running rules against a database with the user who only has the db_owner permission.
- The HTML report exporting option settings in the stand-alone application are not remembered.
- All databases from the chosen Server are checked for permissions when rules are run against one database.
- Required permissions are checked for all existing databases on the chosen SQL Server.
- The following rules fail if the condition is met:
- "Statement without TRY...CATCH".
- "Use of @, @@, or @@ as Transact-SQL identifiers".
- "Space separator for table hints".
- "Schema name not specified".
- "Missing primary key".
- "Missing clustered index".
- Fixes in ApexSQL Generate 2018.01
- "No tables are found in database 'master'" message is shown when trying to load previously saved project where SQL script was used as source of metadata
- The latest loaded project file is not loaded when project where SQL script is used as data source is loaded, and then another saved project is opened, only the title name of the project changes
- "Value cannot be null" error is encountered when loading saved project is being canceled in the process of loading and the Generate button is clicked
- Data is not loaded in the Table mapping window when the same table is selected from another database
- Nothing is exported when one table is checked and the export to CSV is selected
- Nothing is exported when one table is checked and the export to JSON is selected
- Missing the Add value button for the Weighted list (regex) generator
- SQL Server login information are not remembered and the Authentication type is changed to Windows authentication, when a project is saved with SQL Server login information
- "A previous version of ApexSQL Generate was found" message is shown when upgrading to a newer version and the Yes button needs to be clicked multiple times to continue the installation
- "Object reference not set to an instance of an object" error is encountered when the Column selection is clicked after loading another database
- Data from views is not loaded when selected in the Table mapping window
- "Object reference not set to an instance of an object" error is encountered when the Remove button is clicked while saving the Shared generator for IronPython
- "The SELECT permission was denied on the object 'table_types', database 'mssqlsystemresource', schema 'sys'" error is encountered while loading a database from Amazon RDS for SQL Server
- The application freezes when bracket is introduced in the Expression once Cross column generator is selected and calculations are set
- The Excel preview panel is empty and it doesn’t contain any test data when its button is clicked in the View tab
- “Object reference not set to an instance of an object" error is encountered when an expression is inserted in the Weighted list (regex) generator and the Delete button is clicked to remove the expression from the list
- "Index was out of range" error is encountered when exporting table to CSV and opening it through the CSV file tab in the Table mapping window, and then doing the same export to CSV of the same table and opening it again
- "Object reference not set to an instance of an object" error is encountered when selecting object inside the table without checking it, and then using the Cross column generator and switching to Calculations
- "Requested value 'value' was not found" error is encountered when a value is typed into the Category or Type list for the Predefined generator
- SQL Server name is not remembered when the current project is edited
- Missing CLI switches in the Save as batch window for all options that were set in the current project
- "Object reference not set to an instance of an object" error is encountered when SQL script is loaded as a data source and then the Edit button is clicked
- "Object reference not set to an instance of an object" error is encountered when SQL script is selected as a data source and the Table mapping command is clicked from the right-click context menu
- "Object reference not set to an instance of an object" error message is encountered when loading database for the second time from another server
- "String must be exactly one character long" error is encountered when value is inserted into the CSV delimiter text box
- "Path to the SQL script file is invalid. Choose a valid path" message is shown when choosing SQL script as source of metadata
- Wrong data source name is shown in the loading information message when using SQL script as a data source
- "Path to the SQL script file is invalid. Choose a valid path" message is shown when SQL script is loaded as a data source and then the New project is created, where the source is defined to be a database
- The Table mapping feature can be initiated from the right-click context menu in the main grid even when the selected table is unchecked
- A database is not loaded at the first click on the Load button when alias is used for that database
- Tables are not shown after connecting to a database for the SQL table or view generator until connection to another database is established and then connect to the first one
- "Object reference not set to an instance of an object" error is encountered when opening a saved project, clicking on table to preview it and then going to Edit the project and selecting different database with same schema
- Duplicated rows are shown in the Table mapping window when connected to a database
- When the Create one SQL script per object option is selected in the Script tab of the Options window and the OK button is clicked, the setting is not saved and it’s reverted back to the Create one SQL script option
- Missing the SQL script file name when the Create one SQL script granularity option is used to export to SQL
- The given time frame is not applied in the Test data preview for the datetimeoffset data type when assigned with the Random generator
- Dependent objects turn into unchecked ones, when the selection is moved away and brought back to a table for which dependent objects where checked
- When a different Category is selected the last Type that is selected stays the same in the Predefined generator type
- The Seed option should not allow users to add negative numbers, when using the Randomize data by option in the Random type generator
- "Index was out of range. Must be non-negative and less than the size of the collection" error is encountered when using Export to Excel and selecting random drive to export to
- "Could not find file" message encountered when using Export to Excel and creating a new folder to save on desktop
- The application goes into the Not responding state when the Dependent objects panel is turned on from the View tab while the Wide World Importers database is loaded
- The Export window shows information that multiple SQL scripts are generated even though only one SQL script is generated
- The Windows taskbar is not shown on hover, when the Auto-hide the taskbar option is checked, and the application is maximized
- Column generators are used for column names under the Table mapping feature when CSV file is used
- The application is not automatically closed upon finished update process which causes the installation process to be stopped
- The application is integrated in all available SQL Server Management Studio versions even into the ones that were not checked during the installation process
- "Loop option is checked, so Unique option cannot be used" message is shown multiple times when both Unique and Loop options are checked and both options stay checked
- The User defined generator is not shown in the generator list when shared user defined generators are loaded
- Missing the Save as window when saving the user defined generator
- Date and time and Granularity SQL script export options are not properly set as CLI switches in the Save as batch window causing error in the batch script
- None of the checked database options are shown as CLI switches in the batch script
- Incontinences between Live database and SQL script Community edition notices
- "The alias doesn't exist anymore" warning message is encountered when using the Table mapping feature on SQL Azure Database and connecting to SQL Azure Database
- "Cannot connect to ‘DatabaseName’" message is shown when a project file is loaded from the Recent project and the window is closed without prompting the user to enter the password
- The SQL Server Management Studio stops working when Generate test data option is used on a SQL Server Analysis Services instance
- 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 application add-in update window is not shown when SQL Server Management Studio is run and new update is available
- Changes:
- The application now requires Microsoft .NET framework 4.7.1
- Windows Vista and Windows Server 2008 are no longer supported
- Header options under the Script tab in the Options window are now unchecked by default
- The Comments and Print statements options under the Script tab in the Options window are now checked by default
- CLI switch Legal tag [/lt] is now Legal [/leg] switch
- CLI switch Author name [/an] is now Author [/auth] switch
- CLI switches Date time [/dt], Comments [/cmt] and Print statements [/pt] are now values [dt|cmt|pt] of the Output elements [/oe] switch
- Fixes in ApexSQL Script 2018.01
- The Windows taskbar is not shown on hover, when the Auto-hide the taskbar option is checked, and the application is maximized
- Missing the Row filter option for the Structure view
- Missing a step in the installer that will check if there is a previous version installed and to remove it
- The Run executable installer now check-box gets unchecked once clicked the Back button in the Export batch form
- When adding pattern in Object filter step of the wizard, pattern should become active when checked
- The 'loading objects failed' error is encountered if no database is selected when initiating Schema mapping or Object filter
- Default installation folder name is not by standard, it must be “ApexSQL Script"
- The path given in the Output folder text-box is not consistent with the one given in the Save as form when saving the batch file
- Unresponsive progress forms when connecting datasource - selecting Schema mapping or Object Folder
- The Create database option cannot be saved as "my defaults" in the connection form, the structure tab
- Missing the dialog whether to uninstall previous version
- Parsing errors keep reoccurring once encountered
- Automatic updates are not checked by the default
- Indicator of excluded objects doesn't respond in status bar (Data tab)
- Indicator of excluded objects doesn't respond in status bar (Structure tab)
- Lack of summary after scripting process
- The Schema mapping tab is not consistent with other ApexSQL applications
- The Additional scripts tab is not consistent with other ApexSQL applications
- Missing the Logging option in the Package tab
- The Package tab is not consistent with other ApexSQL applications
- 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 aborted, when downloading and installing ApexSQL Script
- "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
- The license file disappears when virtual machine is stopped and then run on Amazon AWS
- 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 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
- 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
- When using Source control as the Output type and clicking on Commit without providing source control credentials. the app crashes
- The Create database option cannot be saved as "my defaults" in the connection form, the structure tab
- When using dual setup monitor environment, sometimes application starts on the secondary monitor even though 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
- Fixes in ApexSQL Unit Test 2018.01
- 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.
- "Unable to get versions info" error occurs when we try to install tSQLt framework from Web source.
- A new query with a unit test template does not open when creating a new test class.
- The first letter of the unit test name will be removed if an empty space is not used when specifying a name of the new unit test.
- SQL Server Management Studio 2012 and 2014 stops working upon starting it with add-in installed from ApexSQL Installer.
- The add-in isn’t integrated into SQL Server Management Studio when it is installed via the Single installer for all tools.