Release candidate for Version 2 is now available, containing several fixes and new features. This release candidate represents Version 2, which is now feature-complete. We will of course continue to add improvements and new functionality to SQLDBcontrol, but any new functionality will not be worked on until after the release of Version 2.
The latest release can be downloaded for evaluation from www.sqldbcontrol.com/beta.aspx.
SQLDBControl
Release 1.9.50000
27 Jun 2008
Feature Additions:
-
Added multi-database query functionality that allows queries to be executed against multiple databases on multiple servers.
-
Added labelling, which allows databases, servers or projects to be labelled. Subsequently, when scripting database objects, it is possible to choose a label from which to script objects.
-
Added the ability to link databases together so that checking an object in/out on one database will check it in/out on the corresponding linked databases.
-
Added functionality to apply source control changes directly to the database without the need to check an object in. This is in effect a self-deployment action.
-
Added the ability to include scripts along with database objects when scripting a database from source control.
-
Added the ability to export the object summary list to .csv.
Code Changes:
-
When viewing T-SQL scripts, the script can be executed even if the object has not been checked out.
-
When deploying objects, a check is now made against the destination object’s definition on the SQL Server
-
and in source control. If there is a difference the latest definition is now retrieved prior to deployment. This is slows down the overall deployment process but it is a necessary check to ensure that all versions of an object’s definition are captured in order to facilitate rollback to a previous state.
-
When deleting object, an entry is now recorded in the object’s history.
-
When scripting database objects, indexed views are now being scripted.
-
Changed the behaviour of double-clicking on an object in the summary list. Instead of expanding the node it now just opens the object.
Bugs:
-
Fixed a bug where the adding a database to a project that does not have any objects would not be allowed.
-
Fixed a bug where tables that once had a text/image column, but no longer do, would incorrectly show up as different to source control.
-
Fixed a bug where adding a view to a project whilst viewing differences would cause an exception.
-
Fixed a bug that prevented two foreign key constraints that referenced the same column (in the referencing table) from being created.
-
Fixed a bug where some index options would not be correctly scripted on a case-sensitive database on SQL Server 2000.
-
Fixed a bug that would cause an exception when renaming a table that had referencing tables that weren’t in source control.
-
Fixed a bug that would prevent indexes being added to newly created views.
-
Fixed a bug where overwriting a checked out object during a deployment would not correctly updated that object’s checked out definition, resulting in a misleading “Object has been modified…” message.
-
Fixed a bug where an exception would occur when adding a View, whose name included single quotes, to project.
-
Fixed a bug where the Query Execution buttons would not be correctly enabled when opening a script.
-
Fixed a bug that would sometimes result in an exception when script views as part of a scripting of objects from source control.
-
Fixed a bug where cancelling the addition of a database into a project could result in subsequent exceptions.
-
Fixed a bug that would result in an exception when displaying objects that included square brackets in the name.
SQLDBcontrol Support
support@sqldbcontrol.com