SQLDBControl 2.2, containing some new features and bug fixes, is now available for purchase and evaluation. Compatibility has been extended in version 2.2 to support Windows 7.
Version 2.2 can be downloaded for evaluation from www.sqldbcontrol.com/download.aspx.
With this version, support for 64-bit installations is now available. If you require a 64-bit installer please contact support@sqldbcontrol.com.
Version 2.2 requires .NET Framework 3.5 sp1, which enables us to offer full compatibility with SQL Server 2008.
Feature Additions:
-
Added “Compare against Label” functionality that allows the source control definition of a database to be compared against a previously-created label.
-
Added option to script objects to multiple files (one for each object).
-
Added a T-SQL Code Formatter to format T-SQL code based on user-defined preferences.
-
Added functionality to allow for the locking of deploy packages. Locking a package prevents any of its associated objects from being edited.
Code Changes:
-
Made necessary modifications to support Windows 7.
-
Increased the command timeout for operations running against the source control database from 30 seconds to 300 seconds. The 30 second limit was being impacted on search packages that involved wide-ranging searches.
-
Modified Difference Reporting such that multiple databases can be selected to form part of a difference report.
-
Modified Difference Reporting so that databases with a compatibility level of less than 80 do not cause exceptions. It should be noted however that databases with a compatibility of less than 80 are not fully supported.
-
Scripts can now be edited even if they are checked out by another user. This allows users to edit scripts for the purpose of executing minor modifications. However, it should be noted that edited scripts can only be saved if they are checked out by the user making the changes.
Bug Fixes:
-
Fixed a bug where tables that had indexes with included columns would show up as different in the summary list when they were in fact not different.
-
Fixed a bug where checking in a table that had indexes with included columns could sometimes incorrectly result in a change script being presented.
-
Fixed a bug where XML indexes were incorrectly showing and ASC or DESC sorting descriptor.
-
Fixed a bug where source control objects that have schema names containing “.” in the name would incorrectly show up as having a different definition to the corresponding server object.
-
Fixed a bug where deployments that contained errors could sometimes be displayed with info icons rather than failure icons and the corresponding error message was not being correctly displayed.
-
Fixed a bug where, selecting a column as identity in the table editor would still allow the column to be defined as nullable.
-
Fixed a bug where InfoTips for system functions would not appear when hovering over function names that were written in lower-case.
-
Fixed a bug where double-clicking on a T-SQL script in the Script Explorer would open the script in Edit-Mode, even if the option to open in read-only mode was enabled.
-
On project start-up, any objects that were to be opened could fail if the server and/or database were offline, and an exception would be generated.
-
Fixed a bug where object parameters would not display when expanding the parameters folder of a SQL 2005/2008 object that had a schema other than “dbo”.
-
Fixed a bug where a carriage return would be missing from objects that had been scripted using the "Script from Source Control" functionality. This in turn could sometimes lead to the keyword GO being appended to the end of scripts rather than on a new line.
-
Fixed a bug where an exception would occur when checking in a SQL Server 2000 table.
SQLDBcontrol Support
support@sqldbcontrol.com