SQLDBControl 2.3, containing some new features and bug fixes, is now available for purchase and evaluation.
Version 2.2 can be downloaded for evaluation from www.sqldbcontrol.com/download.aspx.
Version 2.3 requires .NET Framework 3.5 sp1, which enables us to offer full compatibility with SQL Server 2008.
- Added “Snapshot” functionality to packages that allows snapshots to be taken of Deployment Packages, which provide a snapshot of that package and its object definitions at that point in time.
- Provided functionality to allow packages to be moved from one folder group to another.
- Added functionality to allow databases to be logically moved to another server to reflect database moves on the corresponding physical servers.
- As of this build, if a 64-bit version is installed, the update script will automatically download the 64-bit installer.
- Code has been modified to allow for table column names to have just the case of the name edited, whereas previously this type of modification was only allowed on case-sensitive databases.
- When removing a server from a project, any open objects are automatically closed whereas previously the server removal would be cancelled pending the manual closure of open objects.
- When deleting Package Groups, rather than remove any existing packages they are now simply moved to the parent group.
- Added an informational message when attempting to roll back table changes that indicates it is not possible to roll back table changes.
- Fixed a bug where a period, "." within an object name could cause an "invalid object name" error message.
- Fixed a bug where adding a view from a source database whilst viewing differences would result in a "login failed" error if the source and destination servers used different logins.
- Fixed a bug where scripts within a package could, under certain conditions, display the wrong script path and/or appear twice within the package.
- Fixed a bug where closing a table whilst a grid item was still being edited would result in an exception.
- Fixed a bug where the Intellisense for sp_helptext was incorrectly using the context of the master database rather than the current database.
- Fixed a bug where creating or running a search package would cause an exception if the source control database was created on a case-sensitive SQL Server.