Softpedia >Windows >System >Backup and Recovery >ApexSQL Recover >  Changelog

ApexSQL Recover Changelog

What's new in ApexSQL Recover 2019.02.1262 Patch

May 13, 2021
  • Fixes:
  • 208032: "Not all operations in the set could be loaded" error is encountered when trying to read SQL Server 2008 database on SQL Server 2019

New in ApexSQL Recover 2019.02.1257 Patch (Feb 19, 2021)

  • Fixes:
  • 202743: 'System OutOfMemoryException' error is encountered when executing SQL Server scripts that are over 100GBs in size

New in ApexSQL Recover 2019.02.1254 Patch (Dec 8, 2020)

  • Fixes:
  • "Arithmetic overflow error converting expression to data type int." error is encountered when reading transaction log files for tables consisted of more than 2 billion pages

New in ApexSQL Recover 2019.02.1251 Patch (Aug 28, 2020)

  • Fixes:
  • Connection to a remote SQL Server instance results in a timeout when auditing the remote instance

New in ApexSQL Recover 2019.02.1250 Patch (Aug 14, 2020)

  • Fixes:
  • Connection to a remote SQL Server instance is aborted when large amount of transactions are transferred over the network

New in ApexSQL Recover 2019.02.1249 Patch (Jul 10, 2020)

  • Fixes:
  • Operation data is not shown for compressed nvarchar columns with less than 2 characters

New in ApexSQL Recover 2019.02.1246 Patch (Mar 4, 2020)

  • Fixes:
  • Cannot resolve the collation conflict in the UNION operation
  • Operation data is not shown for tables with page compression

New in ApexSQL Recover 2019.02.1245 (Jan 30, 2020)

  • Fixes:
  • Cannot resolve the collation conflict in the UNION operation
  • Operation data is not shown for tables with page compression

New in ApexSQL Recover 2019.01.1243 Patch (Jan 8, 2020)

  • Fixes:
  • Cannot resolve the collation conflict in the UNION operation

New in ApexSQL Recover 2019.01.1240 (Dec 18, 2019)

  • Enhancements:
  • SQL Server 2019 support
  • Fixes:
  • “Arithmetic overflow error” occurs when auditing database in a simple recovery model in specific case

New in ApexSQL Recover 2018.04.1234 (Jun 21, 2019)

  • 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

New in ApexSQL Recover 2018.04.1219 (Dec 27, 2018)

  • Enhancements:
  • The Primary Key column value is now included in the operation details pane for each operation
  • The application now automatically checks validity of the selected data sources
  • 24h format can now be used in the custom filter when Windows regional format settings imply 24-hour format
  • Column order can now be changed in grid using drag-and-drop
  • Information message added that TDE encrypted database cannot be audited if the afore mentioned database is selected for auditing
  • Information message added that SQL Server instances hosted on Linux OS cannot be audited
  • Fixes:
  • Aborted transactions are not audited
  • Field value grid filter does not affect audited result when applied
  • All conditions aside from the first one in the list are not applied in the field values filter if multiple conditions are defined
  • The application doesn't automatically connect to the audited database when undo/redo script is connected
  • The Find next option does not cycle through the results
  • “Failed to load project” error is encountered when application is restarted with “start as admin”
  • Default value for the custom filter is not set to current day
  • The Ctrl+A shortcut does not work on results audited to grid
  • It is not possible to select last row when undo/redo script is opened via integrated editor
  • The sa login is locked out when wrong password is provided for the sa account
  • “Failed to load project” error is encountered when starting application with insufficient privileges
  • Find panel is not initiated via Ctrl+F shortcut
  • The same SQL Server instance can be added multiple times in the activation panel
  • The displayed count of total rows found when recovering deleted data to a script file does not match the actual count of deleted rows
  • “Object reference not set to an instance of the object” error is encountered when performing recovery from a drop operation on the database for the first time
  • Changes:
  • The application now requires Microsoft .NET Framework 4.7.2

New in ApexSQL Recover 2018.03.1211 (Oct 18, 2018)

  • Enhancements:
  • SQL Server 2019 CTP 2.0 support
  • New error handling and send logs functionality
  • Improved application installer with a dark theme
  • New application icon
  • The ‘Make new folder’ button has been added to all browse for folder dialogs
  • Fixes:
  • Date/time filter is not presented in the regional format if Spanish language and regional settings are used
  • "Object reference not set to an instance of an object" error is encountered when data recovery is performed into a new database in a specific case

New in ApexSQL Recover 2018.02.1203 Patch (May 10, 2018)

  • Fixes:
  • The "Invalid Activation Code" error is encountered when activating application on any SQL Server instance in case that active subscription expires before 10.20.2018

New in ApexSQL Recover 2018.02.1198 (Nov 29, 2017)

  • Enhancements:
  • High DPI and 4K resolution support
  • Log reading is now up to 20,000% faster for all databases that contain over 1,000 SQL tables
  • Fixes:
  • Application stops responding when double-clicking any of the main ribbon bar action icons
  • Both 2017 and 2018 versions are shown in the control panel after update from application version 2017 to 2018
  • The “Unexpected error” is encountered when clicking on Truncated data in the recovery wizard in specific case
  • The “Object reference not set to an instance of an object” error is encountered during recovery of dropped data in a specific case
  • The Show renewal option always resets its state to checked after Options dialog is closed
  • The Get updates dialog is not closed via Esc key
  • The information on application version used to generate the script is incorrect in the commentary of the generated script
  • Changes:
  • New light, blue and dark themes are now available

New in ApexSQL Recover 2018.02.1197 (Nov 28, 2017)

  • Enhancements:
  • High DPI and 4K resolution support
  • Log reading is now up to 20,000% faster for all databases that contain over 1,000 SQL tables
  • Fixes:
  • Application stops responding when double-clicking any of the main ribbon bar action icons
  • Both 2017 and 2018 versions are shown in the control panel after update from application version 2017 to 2018
  • The “Unexpected error” is encountered when clicking on “Truncated data” in the recovery wizard in specific case
  • The “Object reference not set to an instance of an object” error is encountered during recovery of dropped data in a specific case
  • The “Show renewal” option always resets its state to “checked” after Options dialog is closed
  • The "Get updates" dialog is not closed via Esc key
  • The information on application version used to generated the script is incorrect in the commentary of the generated script
  • Changes:
  • Users can now choose between light, blue and dark themes

New in ApexSQL Recover 2018.01.1191 (Oct 26, 2017)

  • Enhancements:
  • Transaction log files and backups can now be read, analyzed and audited
  • Undo and redo script can now be created to rollback or replay DML and DDL changes
  • Auditing results can now be loaded and filtered in grid for forensic recovery and analysis
  • SQL Server 2017 support for Windows instances
  • Fixes:
  • Installer dialog elements will be incorrectly positioned in 4K screen resolution
  • The "A generic error occurred in GDI+" error is encountered when undo/redo script which includes text value with over 10,000 characters is opened in built-in editor
  • The main ribbon button tooltips are not descriptive for the particular option
  • About form doesn't show full license information on used/remaining licenses
  • Release notes link in the upgrade dialog does not lead to the release notes page
  • Options can be selected when clicking on the area to the right of each button in Options dialog
  • Options are not selected in the correct order when using the Tab button to navigate through them in the Options dialog
  • Right mouse button click selects navigation buttons in the grid
  • Excessive empty columns are shown in Field values filter dialog
  • The SQL Server authentication fields are disabled when windows authentication is selected
  • The “last X hours” filter does not properly filter recovery output
  • Changes:
  • The Internal editor is renamed to Integrated editor

New in ApexSQL Recover 2017.01.1180 (May 19, 2017)

  • Enhancements:
  • Support for SQL Server 2017 CTP 2
  • Support for Windows 10 Creators update

New in ApexSQL Recover 2016.02.1166 (Sep 6, 2016)

  • Fixes:
  • Detection of online transaction log and auditing processes are slower up to 1000% on Windows 10 with the anniversary update

New in ApexSQL Recover 2016.01.1164 (Jul 7, 2016)

  • Enhancements:
  • SQL Server 2016 support
  • Users can now choose between 3 themes: white, colorful or dark
  • Fixes:
  • Save as button is not working in the internal script editor
  • Navigating back through active wizard removes provided password
  • The "Could not find file 'ApexSqlRecoverServerRecover.dll' error is encountered when trying to install server side components on the specific SQL Server
  • Trial limits recovery to 1 in 100 instead of 1 in 10 records
  • It is not possible to disable automatic search of available datasources
  • When the recovery/extraction process is canceled, incorrect information that 'recovery is completed' will be shown
  • The 'Script editor' option always reverts back to the 'built in editor' once the options are closed/applied
  • The "Attempted to read or write protected memory" error is encountered when recovering specific database using drop table option
  • Changes:
  • Application now requires .NET framework 4.5.2

New in ApexSQL Recover 2016.01.0109 (Jun 27, 2016)

  • Enhancements:
  • Improved Server overview screen with additional information
  • Improved Database performance view with more database details
  • Improved charts layout and look for faster response and easier navigation
  • Independent baseline calculation for individual metrics
  • The custom central repository database name can be defined by user during the installation
  • Windows credentials can be set by user for adding the SQL Server instance for monitoring
  • Blocking query waits statistics added
  • Query waits alerting based on predefined threshold added
  • SQL Server failover cluster support added
  • Monitor SQL Server agent status added
  • Improved AlwaysOn Availability Group monitoring now fully supports monitoring of all instances in the availability group
  • SQL Server 2016 CTP3 can be monitored and used for hosting the central repository database
  • Message box with critical information, tips and suggestions for helping DBA to understand and analyzing performance issues added
  • Up to 10 times more responsive View alerts char
  • Improved application responsiveness when installed in SQL Server Azure hosted Windows OS
  • Fixes:
  • The date/time text on y-axis of the chart is overlapping when the chart is resized
  • The truncated "No" button the uninstall dialog
  • Once logged in, the user cannot log out from application
  • The "View query plan" doesn't check for the query plan existence and an empty dialog is displayed when query plan is not generated by SQL Server
  • Selecting the zoom level in the Query execution plan viewer dialog corrupts the displayed values of the zoom level
  • When Save is clicked on the Exported reports tab, file will be saved without the file extension
  • Clicking on the View query plan link will not produce any effect or will open just the corrupted dialog
  • After upgrading from the previous version, the MonitorAlerts table schema is not the same comparing to the clean installed version
  • Mouse and keyboard scroll doesn't work in the report preview pane
  • Database report is missing check-boxes for databases selection
  • The Export and Preview button names are not consistent with the similar functionality buttons within the application
  • Once the user log-in requirement is enabled, it cannot be disabled again
  • When selecting reports, the blank page is displayed instead of the menu
  • The Total size changes chart in the "1.1 SQL Server" report doesn’t imply to size of what it is referring and what measurement unit it utilizes
  • The reports cannot be scrolled using the mouse scroll
  • Cursor doesn't change to 'hand' style on the text links
  • Corrupted database names in the table of the Database summary report
  • The 'XDL' files created in SQL 2008 was invalid
  • The "Server health" report title is wrongly used for the "System health" report
  • The SQL Server statistic report displays the name only for the first SQL Server
  • The selected query in the Query performance tab is not marked properly
  • A query selected from the bar chart will not navigate to in the Query performance tab's query list
  • Database list cannot be grouped or sorted by Alerts in the Overview tab
  • Check-boxes disappear from the Alerts pane unpredictably
  • The 'Bytes sent to replica/transport per second' & 'Sends to replica/transport per second' graphs cannot be displayed
  • The 'Receives from replica per second' chart cannot be displayed
  • In the options dialog, adding a color to the graph allows one additional color only
  • The application cannot be started after canceling the upgrade process from a previous to the current version
  • The check all alerts button does not work in the Alerts pane
  • The "Start date and time cannot be greater than ending date and time" error is encountered when trying to set the maintenance period that crosses to the next day
  • The grids highlight visibility is low or doesn't exist when higher contrast monitors are used
  • The data will still be displayed after purging all data from repository database
  • The "An error occurred during data purging." error is encountered when executing the purge for repository database that stores a larger amount of data
  • The query waits total wait time doesn't correspond to the sum of the individual wait type times that are listed for that specific query
  • The query plan link is not available in many cases
  • The defined alert period cannot guarantee the user that alert will not be raised when measured value is above the threshold for the shorter time period than one defined in alert period
  • The application alert tab chart displays the wrong number of alerts comparing to the listed number
  • The charts are rendered empty in all reports
  • The Installer’s Configuration dialog displays most of the active fields as greyed out as disabled style fields
  • The redundant last column in the grid of the 'All instances' dashboard
  • The performance charts display the zero values as gaps, giving the charts corrupted look
  • The Alerting report's "SQL Server active/resolved alerts" table displays the name of the instance as "."
  • The most of reports displays "Not enough data for chart" even when data are present in repository database
  • Inadequate distribution of rights for Administrator users that leads to situation that some users can't be removed at all
  • The alert period doesn't properly suppress the number of alerts and alert will be triggered earlier than alert period time should grant
  • The status alerts are triggered in accordance to the defined alert period, not according to the related state change
  • Charts are not optimized to interpolate values when displaying 30 minutes’ period in case that metric period is set to lover than the default value
  • Removing server can fail in specific cases
  • Configurations child settings overriding is not visible and no indicator that the child setting is different from the parent
  • The "Create SQL Server login (sysadmin)" option in the installer is wrong
  • The alerts for status metrics will not be sent to inform that the alert state has returned to OK state
  • In case of SQL Server where the repository database is down, the application is almost or completely unresponsive
  • The "Provide the required configuration details" sentence is redundantly used in two consecutive sentences in the Setup's Configuration dialog
  • The small initial repository database size causes its quick fragmentation and significant performance decrease
  • The Auto growth value for the repository database is way too small that lead the performance issues because of consuming too many resources for frequent auto-growth
  • The creating firewall exception will open completely the target port, instead to be opened only for application
  • The startup of application is slow when the user login is required
  • There is a memory leakage in application that cause the uncontrolled growth of the used memory and cause application to stop working
  • The "System active/resolved alerts" table in the Alerting summary report displays wrongly the total Server alerts, not only the System alerts
  • The Alerts by metrics table in the alert summary, displays the total alerts number instead of number of the alerts for the selected report period
  • The Alerts by metrics table in the alert summary, displays the total alerts number for SQL Servers not selected for report
  • There is no option to select/unselect all databases for the Database summary report in the Report configuration dialog, preventing the database selection for servers with large number of databases
  • The Database summary report in the Report configuration dialog do not differentiate the user and system databases
  • The Database summary report in the Report configuration dialog do not sort database list by alphabetical and type order making them listed random and hard to locate
  • There is no option to include or exclude system databases from report in the Database summary report in the Report configuration dialog window
  • The exported report will overwrite the existing one without a warning
  • The Alerts by metric table will display all the existing alerts, even when only machine is selected for report and SQL Servers are excluded
  • There are no measurement units for the report charts and tables
  • The Restore defaults option applied to "All instances" will not properly restore defaults for system metrics of the monitored instances
  • There is no progress indicator when adding instances for monitoring
  • The application prevents Windows taskbar to be shown when set to auto-hide the application window is maximized
  • The Avg CPU time chart in the Query performance tab displays the wrong queries in chart
  • The Query performance tab chart' Avg I/O per sec' doesn't have the corresponding column in the table, while other two charts have
  • The Query performance's 'Avg Execution time' charts displays the wrong queries in chart
  • The rows in the Query waits grid are not clickable to allow opening the chart with details for that query
  • The incorrect size of the grid columns of the single queries option in the Query waits tab
  • The database metric tab list of databases does not have appropriate system and user database icons
  • The database metric tab list of databases should list system database at the top and user databases below
  • The devices metric tab list of devices does not have appropriate icons
  • The "System.ServiceModel.FaultException: The server was unable to process the request due to an internal error" is encountered when restarting the application service
  • The queries with the same handle are designated with the different names
  • The SQL handle should be removed from the Query waits tab and moved to tool tip or details
  • The custom tabs are displaying the completely wrong charts, and charts values are wrongly interpolated with other metrics
  • The performance metrics charts are not displayed as interpolated values for 12 hours, 1 day and 30 day period display
  • The number of servers added for monitoring during the trial will not be reduced to the number allowed by license after activation
  • The calculate baselines don't have any progress/work indicator causing the GUI to appears as unresponsive
  • The Query plan viewer window maximizes on double-click on header but not to full screen
  • The Query plan viewer window cuts off the lover part when expanded vertically to a maximum
  • The maximized Query plan viewer window have restore to normal size button but it doesn't have the maximize when not maximized
  • The connection status do not differentiate the actual SQL Server status and availability status of machine that hosts monitored SQL Server
  • The links in Exported reports tab do not match the styles of other links in the application
  • The "System.NullReferenceException: Object reference not set to an instance of an object" error is encountered when Manage databases tab is selected while the selected server is offline
  • The longest running transaction chart displays the worktable transactions time, causing that chart displays only the values for worktables transactions
  • In the Alerts screen entire screen is scrolling without ability to scroll only the grid
  • Changes:
  • Waits stats isolated into separate view
  • History navigation changed to use history slider
  • Redesigned Query waits view
  • Redesigned Maintenance periods view
  • The Configure baselines dialog name is changed to Calculate baselines
  • The "View query plan" title is changed to "Query plan"
  • The default horizontal screen split between the chart and grid is changed to a vertical split
  • The user is not allowed now to turn off the SQL Server status monitoring
  • The system alert action profiles cannot be deleted now

New in ApexSQL Recover 2015.03.0093 (Jun 27, 2016)

  • Enhancements:
  • AlwaysOn Availability Groups performance metrics and the dashboard
  • The built-in Query execution plan viewer
  • Ability to create reports on SQL Server performance is implemented
  • Ability to define users and their privileges is implemented
  • Added notification icon when reviewing charts in a historic view
  • Configuration of metrics per device is implemented
  • Configuration of metrics per database is implemented
  • Added a logarithmic Y-axis scale for Average bytes per write, Free space, Average bytes per read, Available megabytes of memory, Page life expectancy, and Buffer cache hit ratio charts
  • Improved performance base lining with ability to graphically convey medium and high alerts threshold zones in chart
  • Charts loading time improved by up to 100%
  • Charts can now be viewed in time intervals of 12 hours, 1 day and 7 days
  • The application can now display all wait statistic types
  • Fixes:
  • There is no automatic notification on application start, when a new version of the application is available
  • The "Purge data automatically" feature will not purge any data regardless of the parameters set, if the GUI is closed
  • The "An item with the same key has already been added. Type: System.ArgumentException" error is encountered when all parameters of the queries are identical and a query will be missed
  • The "Alert action test executed successfully" message is wrongly displayed when testing query text for custom metrics
  • The newly added custom metric will not be listed in the metric window
  • The time format of the “Last exec time” column in the Query waits tab, is not in the proper time format as it displays a time zone info
  • After change a chart metric via the chart combo box and save layout, the original chart will not be displayed anymore
  • SQL Server and database measurements will not be displayed and instance will be marked as unavailable when removing and then adding again that server instance
  • The "Wait stats" chart doesn't scale Y-axis according to the values of the graphs which could prevent analysis when chart displays one or two wait stats
  • The application allows displaying a baseline threshold graph for more than one metric in charts with more than one metric
  • Having "MSSQL" as part of the name of a named SQL Server instance, will prevent adding it for monitoring
  • The query performance tab tries to load the data even for SQL Server that is stopped for monitoring
  • The "Date" drop down menu in the Query waits tab allows selecting a date even when data doesn't exist for that day
  • The "Query execution plan' filter displays values that are not readable
  • Filter in the query waits dialog remains on the top even when focus is changed to another application
  • The graphical presentation of baselines threshold will be automatically turned off when switching to another tab or window
  • The chart name text is truncated when more than one chart are docked next to each other in a single line
  • Only baseline configurations are deleted when server is removed while baseline calculated values are still stored in the repository database
  • The baseline configuration tooltip is not displayed for all charts for Show/Hide baselines buttons
  • A false error that indicates that the application is not closed, will be displayed during the upgrade process
  • The Wait stats chart will not display anything when SQL Server 2005 is selected in the left pane
  • Parts of the versions description text are truncated in the update service form
  • The databases can be added twice for monitoring in some specific case

New in ApexSQL Recover 2015.02.0087 (Jun 27, 2016)

  • Fixes:
  • The 'Buffer cache hit ratio' metrics are incorrect for some system configurations
  • The "Failed to upgrade database" error is encountered when upgrading from version 2014 to 2015 if the repository database contains a large amount of collected data
  • Vertical scrolling through charts stops when pointer reach the gap between charts
  • The "An item with the same key has already been added. Type: System.ArgumentException" is encountered when all parameters of queries are identical and query will not be collected
  • The Y-axis value of charts will not be updated when the value is out of its current range in some cases
  • The time axis of the Query waits graph utilize the 12h time display without AM/PM
  • The "Purge data automatically" feature will not purge any data regardless of the parameters if GUI is not started
  • The information about the baseline configuration is not displayed anywhere
  • The Question dialog buttons are missing or do not work
  • Base-lining configuration values in "Configure baselines" dialog are always reset to default
  • The column name "Baseline alert" is misleading since it doesn’t enables baseline alerting but baseline thresholds
  • Upper right corner buttons are missing hover over shading
  • Shading in the 'browse for folder' dialog makes selected folder name blend in with shade and hard to see
  • The regional windows settings are not applied to alerts or emails
  • Numeric values have up to 12 decimal places
  • Docking the graphs using the up or down docking wheel arrow, results in graphs cut in half horizontally
  • The sorting does not sort databases per size in the server "Overview" screen
  • If windows resolution is changed while console is active the new resolution parameters will not be applied when resizing the application
  • The "An unhandled exception System.UnauthorizedAccess" is encountered when starting the "View query plan"
  • The column in the Query waits table is truncated and not visible
  • After removing a server instance and adding it again, it will not display any SQL Server or database measurements and will be marked as not available
  • When remote computer that hosts monitored SQL Server instance becomes unavailable, the application will falsely continue to treat these instances as online
  • The "ERROR: Error while trying to get performance counter measurement" is encountered and application will wrongly continue to read the measurements from the unavailable instance
  • The application will allow monitoring of all instances added during the trial, regardless off the allowed number of licenses after activation
  • The left/right scroll buttons in the main tab's ribbon are barely noticeable
  • The baseline configuration settings info is not available to user

New in ApexSQL Recover 2015.01.0083 (Jun 27, 2016)

  • Enhancements:
  • Query wait statistics history and analysis
  • Wait statistics for individual servers
  • Custom SQL Server and database metrics
  • Calculated metrics baselines for desired date range
  • Built-in ApexSQL Deadlock info alert action for analyzing deadlocks
  • Improved server overview and charts loading performance up to 70%
  • One click navigation from dashboard or charts to alerts window and from measurements to query waits tab
  • Fixes:
  • The "Trial period has expired" prompt is not initiated when application is started after trial expires
  • Missing information about number of remaining/used licenses for SQL servers
  • The application experience significant memory leakage and cannot flush unused memory
  • Loading time of "Alerts", "Metrics" & "Server" screens is slow
  • The 'F1' key does not initiate application help
  • The "Metrics" screen became messed completely if the ApexSQL Monitor service is unpredictably stopped for some reason
  • Inconsistent measurement unit for different metrics in the "Database performance" tab
  • The application falsely indicates that the service cannot be located while it is clearly visible that graphs are updating regularly
  • The "Overview" tab displays the wrong OS version on the same machine for different SQL Servers
  • Uninformative message "An error occurred while sending request" is encountered when adding SQL server without located service
  • The calendar-drop-menu title is mostly invisible due to font and background color
  • Click on a database name in the "Overview" tab will always wrongly jump to the master database in the "Database performance" tab, instead on the selected database
  • Error is encountered if "Send logs" is initiated when mail client doesn't exist on the system
  • It is possible to create multiple email profiles with the same name
  • Once created and then closed custom tab cannot be recalled again, instead it must be created again
  • The "ApexSQL Monitor has stopped working" error is encountered when starting ApexSQL Monitor on not fully loaded windows
  • There is an empty (sufficient) column in the "Metrics" screen
  • The application service will not try to restart once it stops unexpectedly and it have to be started manually
  • There is no 'default' metrics setting which user can return to
  • The installer doesn't stop installation when detects that .Net 4.5 isn't installed
  • The "An error occurred while testing the alert action. Please consult application log for details" error is encountered when testing the "Create command" alert action
  • Installer cannot perform upgrade when user console only is installed, but indicate that the full install will be performed
  • The "Add server" dialog cannot list the available SQL Servers in the drop down menu in the remote console
  • The "Jump to end" button navigates chart and sets time to incorrect value
  • Consecutive clicks on the left/right history navigation chart arrows will zoom out the chart
  • The "No series added" message is shown when navigating between alerts and the chart in the "Disk free space" chart
  • Enlarged graphics cannot be closed via 'esc' key
  • Mouse and keyboard scroll do not work in the chart selection pane
  • The monitored database cannot be taken offline as ApexSQL Monitor prevents this operation
  • All measurements after 10th measurement in a single custom chart will be displayed in the single blue color
  • The "System.NullReferenceException" error is encountered when removing the SMTP provider from the combo-box list
  • The "About" dialog wrongly indicates "Professional Version"
  • Selecting the monitored instance that is unreachable for service ends in couple of minutes of completely blank white screen, before the empty graphs are displayed
  • Clicking on the last item checkbox in the "Manage databases" tab list will scroll the list down instead to affect the checkbox
  • "Metrics" tab cannot be scrolled via mouse/keyboard scrolling
  • Copied alert action profile is not named properly
  • Columns doesn't have minimal horizontal size in the "Metrics" screen
  • The "The system cannot find the file specified" error is encountered when trying to execute the action script
  • The parameter value in the test is set at 1000 which is way to high and can cause the serious troubles during the test of some actions
  • The action tag {Server} isn't a fully qualified name causing the script to not execute
  • The query text in the "Query performance" tab cannot display the text from the non-standard code page tables
  • The "Metric name" column is invariably sized wrong by default and it is too wide
  • The "Metrics" tab grid resizes only the "Metric name" column, causing the last column to be cut when resizing
  • The "Email profile" column is too narrow by default and is fixed width, allowing only small amount of characters to be displayed
  • The "Alert action profile" column is too narrow by default and is fixed width, allowing only small amount of characters to be displayed
  • The column auto-size occurs if sorting is changed in the "Query performance" tab
  • The "An error occurred during data purging" error is encountered when trying to purge all data manually
  • Changes:
  • Alerts are displayed per selected server, group or for all instances
  • Metrics are configurable per server, server group or for all instances at once
  • The "Dashboard" screen displays the number of online instead of offline instances
  • CPU, disk, memory and databases alerts are displayed in the "Dashboard" screen
  • Up to 10 metrics can be displayed in a single chart at once
  • "Show previous series" and "Show next series" chart buttons are added for navigation between metric sets for charts with more than 10 metrics
  • Restyled metrics and alerts tables
  • "Manage email profiles" and "Manage alert action profiles" links are displaced from the "Metrics" screen to corresponding dropdown menus
  • SQL Server instances hierarchy pane is removed from the "Metrics" screen
  • The "Back to charts" button is added in "Alerts" and "Metrics" screens for easier navigation back to charts
  • "Select action tag test data" dialog is added for inserting the test values for tags when testing created alert action or custom metric query
  • New alert action tags "{ServerFullName}" and "{DefaultPath}"

New in ApexSQL Recover 2014.04.1135 (Jan 22, 2015)

  • Fixes:
  • The "Could not load file or assembly" error is encountered when recovering database without transaction log files
  • Server choice is not locked in the "Connect to server" dialog in the activation form
  • Object filter in the "Select the tables to recover" step of the recovery wizard is missing the drop-menu with existing schemas
  • Incorrect message is displayed when connecting to the unsupported SQL Server
  • The "Release notes" link in the "Update" dialog leads to an incorrect location
  • Changes:
  • The recovery feature "From corrupted database or MDF file" has been discontinued

New in ApexSQL Recover 2014.03.1129 (Jan 22, 2015)

  • Fixes:
  • The "Could not load file or assembly" error is encountered when recovering a deleted structure and data to a new database
  • The number of recovered tables during the trial period is limited to 1 out of 10
  • Recovery process cannot be performed directly to the database when recovered tables have IDENTITY property
  • The "External component has thrown an exception" error is encountered when trial period is extended on remote SQL Server
  • The "Adding a server failed" error is encountered when activating a server that has the same name as already activated other server, but has a different system name
  • The "Update error: Unable to load one or more of the requested types" error is encountered when trying to update the application

New in ApexSQL Recover 2014.02.1116 (Oct 16, 2014)

  • Fixes:
  • The application requires to be run with the Windows "Run as administrator" option on specific Windows configurations

New in ApexSQL Recover 2014.01.1112 (Oct 16, 2014)

  • Enhancements:
  • Easier Server side components installation for remote servers
  • Server side components are no longer necessary when recovering a local database
  • The application now fully supports SQL Server 2014
  • Fixes:
  • The "The specified schema name "" either does not exist or you do not have permission to use it" error is encountered when recovering a table with a non-default/existing schema
  • The "Unexpected error - Attempted to read or write protected memory. This is often an indication that other memory is corrupt" error is encountered when recovering deleted data from specific databases
  • The main form flickers when selecting areas in the left menu
  • The application cannot automatically detect the database recovery model
  • Changes:
  • A new UI style

New in ApexSQL Recover 2011.03.1061 (Oct 18, 2013)

  • Enhancements:
  • The application now fully supports Windows 8.1
  • Options for setting the intermediary and output folders have been introduced
  • Fixes:
  • Rows from a partitioned table cannot be recovered if the online transaction log is not selected as a data source
  • When SQL Server Service is running under a Network Service or Local Service account, the application stores all server side log files and metadata in the C:\Windows folder

New in ApexSQL Recover 2011.02.1058 (Oct 1, 2013)

  • Fixes:
  • The information about the trial version limitation is not shown in the application

New in ApexSQL Recover 2011.02.1057 (Oct 1, 2013)

  • Fixes:
  • 1 out of 100 records, instead of 1 out of 10, is recovered in trial mode

New in ApexSQL Recover 2011.02.1056 (Oct 1, 2013)

  • Fixes:
  • Large data chunks could not be read in compressed backups

New in ApexSQL Recover 2011.02.1055 (Oct 1, 2013)

  • Enhancements:
  • Recovery from SQL Server 2012 databases is fully supported including:
  • Dropped FileTables recovery
  • Lost FileTable data recovery
  • Natively compressed transaction log and database backups can now be used as data sources for recovery
  • Visual C++ run-time components are now installed on a remote server automatically during Server Side Components installation
  • Numeric data stored in the vardecimal storage format can now be recovered
  • Data lost due to TRUNCATE and DROP operations can now be recovered directly to a database
  • FILESTREAM data can now be recovered from database backups
  • Improved usability: the following filtering options have been introduced to specify the time frame in which the incident had occurred:
  • Last 60 minutes
  • Last 24 hours
  • Last 7 days
  • Last 30 days
  • A customizable date and time picker
  • Date and time are unknown
  • Tables can now be recovered directly to a database in the following scenarios:
  • User defined data type definitions are missing for the tables being recovered
  • The tables being recovered contain calculated columns
  • Schema definitions are missing for the tables being recovered
  • Fixes:
  • Local CHM help file is not used when available
  • Invalid default file name is generated for the recovery script if the network protocol is specified explicitly as a part of the server name
  • No icon is displayed in the header of the Additional data sources step in the ‘Recover lost data due to a DROP TABLE operation’ wizard
  • ApexSQL Log icon is used in the Uninstall Server Side Components dialog
  • Presence of the required .NET Framework service pack is not verified prior to installation
  • Server Side Components always show as not installed in the Server Activation Center dialog if the machine name of the local server was specified as '.'
  • The Server Activation Center dialog has no minimal size constraints
  • The generated recovery scripts lack table header and footer
  • The recovery script path is not preserved within a session
  • By default, tables are displayed in the ‘Recover lost data due to a DELETE operation’ wizard are shown as deselected
  • Options dialog tooltip icons have a background when Windows Classic theme is used
  • Nothing is recovered from a detached MDF file residing on a remote server
  • A detached MDF file is mentioned incorrectly as an additional data source available for recovery in the ‘Recover lost data due to a DROP TABLE operation’ and ‘Recover lost data due to a DROP operation’ wizards
  • Unnecessary empty spaces are added to the bottom of the generated recovery script when the transaction log processing is performed on the server
  • BLOBs may be recovered incorrectly when transaction log processing is performed on the server
  • "Connection to master database failed" error message is displayed in the Select data sources step of the Recovery wizard if the specified database backups are no longer available
  • "Connection to master database failed" error message is displayed when connecting to a remote server in the ‘Recover table data from a database backup’ wizard
  • The recovery script generated for objects containing apostrophes (‘) in their names has syntax errors
  • Changes:
  • The application now requires .NET Framework 3.5 SP1 to run properly

New in ApexSQL Recover 2011.01.1031 (Nov 7, 2011)

  • Enhancements:
  • Application now supports recovery from SQL Server Denali CTP3 databases
  • Application can now write recovered data directly to a database
  • Application will now run as 64-bit process under 64-bit OSes
  • Recovery from page and row compressed tables is now supported
  • Recovery from SPARSE columns is now supported
  • New main dialog that lists all available actions has been introduced for improved usability
  • Recovery wizard has been redesigned for improved usability
  • New standard Options dialog available from the main dialog through Options link has been introduced
  • Server Usage options group has been added to Options dialog to control whether to perform recovery on the server. Available choices are Off (default), On and Auto
  • New Resources link has been introduced to the main dialog for quick access to Help page, Support forum, Training page, FAQs, Knowledge base, Troubleshooting, About and Get Updates dialog boxes
  • New Server Activation Center dialog has been implemented for Server Side Components management
  • All appropriate application and Recovery wizard options have now a tooltip with a description
  • Administrative privileges are no longer required for startup but only for Server Side Components installation
  • Fixes:
  • Incorrect recovered row count is shown for lost objects recovery
  • Application is unable to connect to default SQL Server 2008 instance
  • Table DDLs are not recovered with ‘Recover from corrupted database or detached mdf’ recovery option
  • Offline databases can be selected for recovery
  • System.NullReferenceException exception is encountered on attempt to use HyperBac backup file in recovery
  • Application does not check for updates on startup
  • “Couldn't retrieve table” error is encountered when recovering table data from SQL Server 2000 backup
  • "Unclosed quotation mark after character string" error is encountered when executing recovery script that contains uncommon characters that require quotation or line breaks
  • “sys.sysrowsets could not be located” error is encountered on attempt to use transaction log backup with block size of 65,536 in recovery
  • Application fails to check for updates on Windows Server 2003
  • Online transaction logs are not selected by ‘Several sources are available for data recovery’ Data Availability setting by default
  • System.NullReferenceException exception is encountered on attempt to recover BLOBs from detached database or database backup of bad format
  • Output path setting is not remembered within application session
  • Changes:
  • Select Recovery option step options have been moved the main application dialog
  • Server Side Components of all older versions will now be uninstalled from the server when installing a newer version
  • Progress dialogs have been updated to be more standard with other applications
  • Setup Server-side Components dialog has been deprecated

New in ApexSQL Recover 2008.06.0838 (Mar 25, 2010)

  • Fixes:
  • Server-side components installation fails on Windows Vista/7 with UAC turned ON
  • Server-side components installation fails if the application extended stored procedure DLL (ApexSqlRecover2008Xprocs.dll) is locked by SQL Server
  • In rare instances, SQL Server service stops when installation of server-side components fails because UAC is ON for Windows Vista/7 and/or the application extended stored procedure DLL (ApexSqlRecover2008Xprocs.dll) is locked by SQL Server
  • In rare instances, data isn't recovered from deleted columns that have a BLOB data type
  • Transaction log reading is unnecessarily extended beyond limits specified in time range filter causing unnecessary slowdowns during recovery
  • When installing server-side components in Windows XP and when the SQL Server service is running under a Network Service account, a login dialog is sometimes unnecessarily displayed
  • Redundant logging can cause unnecessary slowdowns during recovery and uncontrollable growth of application log files
  • Changes:
  • The following new messages can now be shown during installation and execution of server-side components:
  • Insufficient permissions to execute server-side components. Please make sure SQL login used has EXECUTE permission on ApexSQL Recover extended procedures (ApexSQLRecover2008XProcs.dll).
  • Insufficient permissions to install server-side components. Please make sure you're a member of the sysadmin server role.
  • Insufficient credentials to install server-side components. Please check user name, password and/or domain name

New in ApexSQL Recover 2008.05.0834 (Mar 16, 2010)

  • Enhancements:
  • BLOB reading now consumes less memory (up to 50% less)
  • Fixes:
  • It's impossible to connect to SQL Server using Windows Authentication under Vista with active UAC
  • When a machine’s hardware ID changes, the server's activation status becomes invalid and re-activating is not possible
  • "Unknown SQL Server version" error is received when reading SQL Server 2000 backups
  • Online transaction log files sometimes cannot be accessed on an x86 OS that has more than 4GB of RAM
  • The application fails when trying to read SQL Server 2000 database backups
  • Servers with expired evaluation can’t be activated
  • Online transaction log and database files hosted on Windows 2000 cannot be read
  • Transaction log backups are incorrectly shown on Add Data Sources step
  • System.Exception exception is received when accessing Activate Product command from Help menu after Server-side Components were uninstalled
  • Credentials aren’t verified when activating a server with the use of SQL Server Authentication so user cannot connect
  • Changes:
  • Server-side components have been split to two independent sets: server-side components for ApexSQL Log and server-side components for ApexSQL Recover. On upgrade, un-used server-side components are deleted
  • Split ApexSqlServerXprocs2008.dll into ApexSqlLog2008Xprocs.dll and ApexSqlRecover2008Xprocs.dll
  • Split ApexSqlServerHelper2008.exe into ApexSqlLog2008ServerHelper.exe and ApexSqlRecover2008ServerHelper.exe
  • Split ApexSqlServerHelper2008.sys into ApexSqlLog2008ServerHelper.sys and ApexSqlRecover2008ServerHelper.sys
  • All server-side logs for the application’s server-side components are consolidated into one log file: ApexSqlRecover2008.log
  • The following error messages have been replaced with more informative equivalents:
  • "Unknown error code: 128 during activation"
  • "ApexSqlServerHelper2008 failed: OpenSCManager() failed: Access is denied. (error code = 5)"
  • "Copy file for ApexSqlServerXprocs.dll failed: The system cannot find the path specified. (error code = 3)"
  • "Cannot access transaction log file"
  • "CreateService() failed: The specified service has been marked for deletion"
  • "ApexSqlServerHelper2008 failed: log2::lnhf::GetFileDeviceName: Access is denied."
  • All application logs, both client and server-side, are now in UNICODE
  • Evaluation period for each server has been changed from 30 days to 14 days

New in ApexSQL Recover 2008.01.0609 (Mar 16, 2010)

  • Enhancements:
  • Added Main Menu to the application
  • Added option to recover BLOB data as files
  • Ability to recover data from database backups (BAK files)
  • Ability to select specific tables when recovering data loss from detached databases or database backup
  • Ability to install or uninstall server-side components from a server
  • Added Summary screen at the end of wizard showing recovery process information
  • Added option to show generated T-SQL recovery script in internal editor or in system default associated editor (in case the script is too big in size)
  • Added support for new SQL Server 2008 types: DATE, DATETIME2, DATETIMEOFFSET, TIME, HIERARCHYID, GEOMETRY, GEOGRAPHY
  • Added integrity check for server-side components.
  • Added tabled IDs to CREATE/DROP TABLE statements.
  • Improved statistics logging for queries and global memory.
  • Ability to open directory where application log files reside.
  • Changes:
  • Removed database selection when recovering data loss from detached databases or database backup
  • Removed ability for custom selections (check boxes) in Table Selection and Detached/Backup Selection steps
  • Moved application log and other temporary application files from "Program Files" to user's own directories.
  • Fixes:
  • Fixed a performance problem when reconstructing updates on tables with clustered indexes.
  • Fixed a minor problem with application's finalization.
  • Fixed a minor problem with logging.
  • Fixed a problem with MONEY and SMALLMONEY formatting.
  • Location of activation form is always top left corner
  • The same shortcuts are for finish and File menu (Alt+F)
  • The same shortcuts are for Help menu and button (Alt+H)
  • Typo in the description for the BLOB data recovering
  • Lack of space in activation dialog title
  • Activation dialog does not become active when select ApexSQL Recover from task panel after installation of server-side components is finished
  • Different activation dialogs appear on application launch and from About dialog
  • Application invokes error if ApexSQL Recover server-side components were installed over ApexSQL Log server-side components
  • Incorrect description for dropped objects recovery
  • Incorrect description for “no data source available” option in the recovery from DELETE operation section
  • ApexSQL Recovery components are not compatible with 2005.11.0534 ApexSQL Log release
  • All BLOB data recovers instead every 10th under trial license
  • State of server-side components is determined incorrectly
  • ApexSQL Recover is unable to recover data from DELETE operation
  • Incorrect info is displayed for really recovered BLOB data
  • Incorrect information about recovered rows in the Detach recovery for MS SQL 2000
  • Application tries to connect to database from the previous session
  • Selected database has no respective icon
  • Application does not remember Output Path during one session
  • On-Server installed application components are not activated
  • Online transaction log is always used instead of checked transaction log backup

New in ApexSQL Recover 2005.10.0502 (Mar 16, 2010)

  • Enhancements:
  • Added support for ApexSQL Log API (MAJOR ENHANCEMENT)
  • Further improved quality of UPDATE reconstruction process (MAJOR ENHANCEMENT)
  • Added support for online transaction log reading on Vista 64-bit and Windows 2008
  • 64-bit (MAJOR ENHANCEMENT)
  • Added experimental support for Itanium (IA64) platform for both SQL Server 2005 IA64 and
  • SQL Server 2000 64-bit.
  • Added experimental support for SQL Server 2008 on all platforms.
  • Added support for INSERT and DELETE operations affecting more than one row to auditing and exports.
  • (added "ROW_ORDINAL" to LOGNAV_RECORD table, "row_ordinal" tag to XML export and "Row Ordinal" to CSV export.)
  • Improved the performance of table, user name, application name and client host filtering.
  • Improved scaling for large auditing sets in GUI.
  • Improved overall scaling.
  • Added REDO/UNDO mark to REDO/UNDO scripts.
  • Added table existence check in DDL statemens in recovery scripts.
  • Added recovery of user defined data types from detached MDF files.
  • Changes:
  • Renamed xp_ApexSqlLogMonitor_* extended procedures to xp_ApexSqlConnectionMonitor_*
  • Removed LOGNAV_RECORD2 primary key from LOGNAV_RECORD table and added LOGNAV_RECORD3 primary key.
  • Fixes:
  • A problem when multiple transaction log backups are specified (MAJOR FIX)
  • A crash during exporting (MAJOR FIX)
  • A resource leak problem after auditing is finished affecting memory and other resources (MAJOR FIX)
  • A problem with Connection Monitor stopping to capture logins without restarting (MAJOR FIX)
  • A problem with BLOB recovery sometimes not working correctly when doing recovery from detached MDF files (MAJOR FIX)
  • A problem with online transaction auditing on Vista.
  • A problem with filtering of users retrieved uniquely by SID.
  • A problem with Connection Monitor when TCP/IP connections are disabled.
  • A problem with new user names, application names and client hosts filters not included
  • by default in the filter even when all names were previously selected.
  • A problem with invalid XML characters in XML output.
  • A problem with auditing read-only databases.
  • A warning messages in generated BULK scripts.
  • A problem with UPDATE operations logged due to change in table schema.
  • A problem with some UPDATE operations not being used in UPDATE reconstruction.
  • A problem with operations on forwarded stub rows passing through as data row operations.
  • A problem with not showing types of values in SQL_VARIANT fields.
  • A problem with resulting XML file when /no_header switch is specified.
  • A problem with resulting XML file when /append switch is specified.
  • A problem with status bar not updated when no operations are found.
  • A problem with no refresh of progress bar before first operation is found.
  • A problem with "Cancel" button being the default button in Recovery Wizard.
  • A problem with long-running server operations giving time-out error.
  • A problem with missing timestamp column value in WHERE clause of UNDO/REDO scripts even when it's part of PK/clustered index.
  • A problem with running Recovery Wizard from Server Explorer when using SQL Server authentication.
  • A problem with SQL Server authentication form demanding non-empty password.
  • A problem with transaction log backups sometimes not automatically offered by Log Selection Wizard.
  • A problem with showing user's SQL login name instead of NT user name when both have the same SID.
  • A problem with recovery of deleted rows from transaction logs when under evaluation.
  • A problem with connection "leak" in Recovery Wizard.
  • A rare problem with mixup of db ID, file ID and transaction log file names.
  • A rare problem with reconstruction of variable-length columns data.
  • A rare problem with output of tag in XML export.
  • A rare problem Connection Monitor not working on default SQL Server instances.
  • A rare problem with default server name in setup.
  • A rare problem with some transaction log operations not being loaded.
  • An unclear error message when accessing online transaction log files in SIMPLE recovery mode.
  • Various problems in error, warning and information messages.

New in ApexSQL Recover 2005.04.0453 (Mar 16, 2010)

  • Greatly improved reconstruction of UPDATE operations (MAJOR ENHANCEMENT)
  • Greatly improved memory footprint and performance scaling (MAJOR ENHANCEMENT)
  • Added support for recovery of VARCHAR(MAX), NVARCHAR(MAX) and VARBINARY(MAX) data types from
  • database files (MAJOR ENHANCEMENT)
  • Improved support for transaction log backups converted from 3rd party backups (MAJOR ENHANCEMENT)
  • Added partial reconstruction of changes made to fixed-length fields in UPDATE operations.
  • Added partial support for recovery of XML data type from database files.
  • Added support for reading SQL Server 7/2000 transaction logs under SQL Server 2005.
  • Added support for reading SQL Server 2005 transaction logs under SQL Server 7/2000.
  • Added more recovery reports details to recovery scripts.
  • Added dummy data to BLOBs that are partially recovered due to lack of data.
  • Added "row partially reconstructed" column to SQL, BULK, CSV and XML exports.
  • Added "/run_small" switch to command line interface which forces the application not to save
  • most of intermediate files on the hard drive. If there is less than 5% free space on the drive
  • the application will switch automatically to "run small" mode.
  • Added recovery script path selection to Recovery Wizard.
  • Added table mapping to MDF data recovery.
  • Improved generated recovery scripts for less-than-perfect data recovery scenarios.
  • Improved progress bar during transaction log reading.
  • Improved reliability of BLOB recovery algorithm.
  • Improved auditing performance in general.
  • Improved memory managment when under memory pressure.
  • Improved formatting for REAL and DOUBLE SQL types.
  • Improved diagnostic logging.
  • Integrated client-side and server-side setups into one setup.

New in ApexSQL Recover 2005.01 (Mar 16, 2010)

  • Fixed a problem with Recovery Wizard toolbar button leading to exception (MAJOR FIX)
  • Fixed a problem with persisted computed columns lacking name in the grid under SQL Server 2005 (MAJOR FIX)
  • Fixed a problem with remote uninstall when repairing previous installation (MAJOR FIX)
  • Fixed a rare problem with _variant_t conversion exception under some instances of SQL Server 2005.
  • Fixed a problem with remote install.
  • Fixed a problem with exception "Invalid object name 'msdb.dbo.APEXSQL_LOG_LOGIN'" on User ID filter page.
  • Fixed a rare problem with ApexSqlLogXprocs.dll unload.
  • Fixed some command line interface error messages.
  • Fixed a problem with grid refresh resetting checked rows.
  • Fixed a problem with SPID filtering in GUI.
  • Fixed a problem with row history grid showing wrong row in the main grid.
  • Fixed a problem with Find dialog with no now rows in main grid leading to exception.
  • Fixed several minor visual issues.

New in ApexSQL Recover 1.85 (Mar 16, 2010)

  • Fixed a problem with not processing ALTER PROCEDURE/VIEW/TRIGGER/FUNCTION in DDL auditing (MAJOR FIX)
  • These DDL operations are now shown as a combination of CREATE and DROP operations since they are logged so.
  • Fixed a problem with memory not being freed correctly in some circumstances (MAJOR FIX)
  • Fixed additional transaction information loading performance problem.
  • Fixed a problem with reading of online and detached log files.
  • Fixed a problem in using Live Log for databases with invalid identifier for name.
  • Fixed XML export end tag.
  • Fixed BULK export script problem when using absolute paths for bulk files.
  • Fixed "This key is already associated with an element of this collection" problem.
  • Fixed login information being lost when open log fails.

New in ApexSQL Recover 1.81 (Mar 16, 2010)

  • Fixed two problems with Log running on Windows NT 4 and below.
  • Fixed a problem with SQL Script export.
  • Fixed a rare GPF problem

New in ApexSQL Recover 1.70 (Mar 16, 2010)

  • Enhancements:
  • Improved Connection Monitor's start time.
  • Improved performance for Live Log when accessing online logs on remote machines.
  • Added finish times to XML and SQL export files.
  • Improved performance for CSV and SQL export.
  • Removed limitation of max. 10,000 operations in operations grid.
  • Added wildcards for input files (like backups) to command line interface.
  • Added new filter switches to command line interface:
  • "applications" - filters operations per user applications
  • "hosts" - filters operations per client hosts
  • "spids" - filters operations per SPIDs
  • Added dropped tables mapping switch "mapped_tables" to command line interface.
  • Added export header suppression switch "no_header" to command line interface.
  • Added "UNKNOWN(id)" text for unknown tables to SQL export.
  • Improved command line interface error reporting.
  • Expanded and improved help file.
  • Fixes:
  • Fixed a problem with disappearing rows in operations grid.
  • Fixed a problem with filters sometimes being too permissive.
  • Fixed a problem with REDO/UNDO scripts when string fields contained apostrophe.
  • Fixed a problem with command line interface and parsing of quoted file names.
  • Fixed a GPF problem when opening two or more transaction log backups or detached logs at the same time.
  • Fixed a missing quote in CSV export.
  • Fixed a problem with missing logins in connection monitor.
  • Fixed a problem with Connection Monitor not shutting down correctly.
  • Fixed a problem with Connection Monitor not freeing LogNavXp DLL.
  • Fixed a problem with quotes in UNDO/REDO scripts.
  • Fixed a NULL in quotes value in SQL export.
  • Removed database roles from the list of users.
  • Changes:
  • Removed the syntax coloring in the export preview window due to the problems with amount of exported data.

New in ApexSQL Recover 1.52 (Mar 16, 2010)

  • Enhancements:
  • SQL and XML syntax coloring.
  • Added case-insensitive and whole-value fields filtering.
  • Added filtering of "ShrinkFile" and "MoveIndexPage" transactions.
  • Improved connection monitoring response times.
  • Faster online logs analysis.
  • Fixes:
  • Fixed a GPF problem when auditing backup files.
  • Changes:
  • Changed to immediate response when refreshing.

New in ApexSQL Recover 1.43 (Mar 16, 2010)

  • Fixes:
  • Several GPF fixes.
  • Changes:
  • Completely redesigned Live Log removing the any need for enabling/disabling Live Log during log shrinking as well as having "autoshrink" option turned to off. (MAJOR CHANGE)

New in ApexSQL Recover 1.31 (Mar 16, 2010)

  • Fixes:
  • Fixed a "Live log server-side components are not correctly installed." issue (MAJOR FIX)
  • In SQL Script export, limited the size of exported values to 3800 characters.
  • Changes:
  • Removed possibility for Live Log to work on "autoshrink" databases.
  • Changed command line to use database's online logs if no source is specified.
  • Added "timing" option to command line interface.

New in ApexSQL Recover 1.22 (Mar 16, 2010)

  • Fixes:
  • Fixed a problem with reading of transaction log backups.
  • Fixed a problem with reading of live and detached logs.
  • Fixed a problem with historic reconstruction and automatic UPDATE reconstruction.
  • Fixed a live log refresh problem.
  • Fixed a command line parsing problem.
  • Fixed a command line and trial expiration problem.
  • Changes:
  • Added LSN column for operations. LSN (Log Sequence Number) uniquely identifies
  • operations on the level of database and it can be used to order operations in
  • the sequence in which they happened.
  • Added "Request support" option for error messages.
  • Reorganized help file to ease navigation.
  • Sorted user list in the filter option.
  • Rearranged table and user filter pages.

New in ApexSQL Recover 1.11 (Mar 16, 2010)

  • Enhancements:
  • Added generation of UNDO/REDO scripts.
  • Added "Options" dialog [Tools->Options] with following options:
  • -Number of rows for "show more rows" action
  • -Turn on/off alternative transaction coloring
  • Removed automatic filtering of operations on nonexistent tables.
  • This can now be configured in Filtering dialog.
  • Added option to select multiple rows.
  • Added [Export as...] options that work on selected rows only.
  • Fixes:
  • Fixed a rare problem with auditing of live logs.
  • Fixed server name in open log dialog.
  • Fixed default filenames for export options.
  • Fixed a problem with computed columns.
  • Fixed a problem with the time range filter.
  • Fixed formatting of SMALLDATETIME values.
  • Changes:
  • Now when refreshing log, database structure is also refreshed.
  • Added FAQ to help file.
  • Added "Clear filter" option [Edit->Clear filter]
  • Added better description for "log file not found" error.
  • Added timestamp to exported files.
  • Added milliseconds output to DATETIME values.
  • Various minor enhancements to UI.

New in ApexSQL Recover 1.1 (Mar 16, 2010)

  • Enhancements:
  • Added "Type" column to row details.
  • Added live log server-side components' version checking.
  • Fixes:
  • Fixed "freeze" problem occurring after unsuccessful connections to logs.
  • Switched to 14 days from day of installation trial period.

New in ApexSQL Recover 1.00 (Mar 16, 2010)

  • Added "busy" dialog for long running operations.