Version 1.4 is available!

Version 1.4 contains a large number of new features, enhancements and fixes.

The latest release can be downloaded for evaluation from www.sqldbcontrol.com/download.aspx.

If you are an existing customer you can download the latest version by logging into your account.

IMPORTANT UPGRADE INFORMATION:

Because of the large number of changes that have gone into version 1.4 we recommend you backup your existing source control database and label it accordingly prior to upgrading.

In a multi-user environment, once you have upgraded to version 1.4, all users of SQLDBcontrol must also upgrade to version 1.4.

There is a bug that prevents the latest version from being dowloaded unless you are doing so from withing a project

SQLDBControl

Release 1.4.00000 

13 Nov 2006

Feature Additions:

1. Added a T-SQL Scripts folder to the Project Explorer that enables T-SQL scripts to be created without associating them with a database.
2. Added the ability to lock dockable controls in place so that they cannot be accidentally moved.
3. Added “Go to Definition” functionality by pressing F12 whilst the caret is positioned on an object name inside an editor.  Pressing F12 opens the object under the caret position if that object is part of the project.
4. Added an option in Tools > Options to allow setting the default double-click behaviour on objects in the summary list.  By default objects are opened for editing.  If the option is disabled then objects are opened in read-only mode when the object is double-clicked (unless the object is checked out by the person double-clicking on it, in which case it is always opened for editing.
5. Added Deployment Packages.  Deployment Packages are a collection of objects (including scripts) that are logically grouped together for the purpose of deploying them to other databases.
6. Added an option to Enable/Disable the appearance of SET ANSI_NULLS and SET QUOTED_IDENTIFIER statements when viewing object definitions.
7. Added Export to CSV and Export to HTML context menu options in the results grid of query results that are output in grid format.
8.  Added Print context menu options in the results grid of query results that are output in grid format.
9.  Added InfoTips when hovering over system data types, declared variables, system variables, set statements and dbcc statements.
10.  Added Object Search functionality, allowing for string search capabilities on objects within projects.  Search results are automatically saved, allowing the results to be viewed at a later date.
11. Added a Deploy Timeout option under Tools > Options (Deploy Tab).  The value controls the command timeout value for objects/scripts that are being deployed.  By default this value is set to 0, which indicates there is no timeout.
12. Added an Option in Tools > Options so that databases will not get returned in Intellisense for objects.  With the option disabled, only local tables will appear in Intellisense (e.g. “select * from...”).  With the option enabled (default) databases will appear in the Intellisense list prior to the tables – this enables cross-database queries to be written more effectively.
13. Added Intellisense that displays relevant objects in the current database after sp_helptext has been entered.

Code Changes:

1. Changed behaviour of Select area in Object Summary Tab such that check boxes now remain checked and corresponding records are selected accordingly.
2.  Included "begin try…end try” and “begin catch…end catch” statements as collapsible nodes in the editor.
3.  The position and size of the main application window is saved so that the next time the application is opened, the size and position are maintained.
4. Improved performance of retrieving the list of object dependencies.
5. When selecting objects from the object list, the object selected for the given server, database and object type combination is remembered so that the same object will remain selected when returning to the same list.
6. When saving an object, only changes made to the actual definition of the object are saved.  Any changes (other than SET ANSI_NULL or SET QUOTED_IDENTIFER changes) that occur beyond the bounds of an object’s definition are not saved.  The boundary markers for an object’s definition are the GO identifiers that occur immediately before and after an object’s CREATE/ALTER statement.
7. Changed the way in which object references are returned such that performance has been improved.
8. Added parse query button that allows for the currently selected text to be parsed instead of executed.
9. Moved the Check In, Check Out and Undo Checkout buttons to the main tool bar so that they are accessible when editing objects in the editor.
10. Extended Context Menu in the Object Summary to allow for new objects to be added.  This complements the same functionality that can be accessed from the Project Explorer context menu and buttons in the Project Explorer button bar.
11. Variables in IntelliSense lists now appear in alphanumeric sort order.
12. When building an IntelliSense list for select statements, if the statement only consists of one table and it does not have an alias, the table’s column list is displayed.
13. When displaying a list of columns within insert and update statements, pressing the comma would display the Intellisense list of remaining columns immediately after the comma.  Pressing comma now inserts a space immediately after the comma, after which the list is displayed.
14. When typing out insert statements using INSERT INTO [table]…VALUES, when entering the VALUES part of the statement an InfoTip matching the columns in the INSERT INTO part of the statement is now displayed.
15. Improved Intellisense in various areas.
16. When performing an Undo CheckOut operation the last updated date and last updated by values are reverted to the values prior to the object being checked out.
17. Added a message box that shows status information and error messages in the Deploy Status screen.  This replaces the column that showed the error messages previously.
18. When recovering a deleted object checks are now performed to see if the object about to be recovered already exists on the SQL Server and if its definition is different.
19. Improved performance of scripting SQL Server 2005 objects.
20. Double-Clicking a display error in the results window will select the line on which the error occurred within the query editor.
21. Added ability to rename scripts.
22. When opening an object in the object editor, the object’s CREATE statement is now replaced with an ALTER statement to remove the need to manually change this.
23. When performing a Find (Ctrl-F) in an editor, after the Find dialog window has been closed the F3 key can be used to find the next item (assuming a value for the Find text box was supplied).
24. Improved formatting of InfoTips and also added relevant icons to them.
25. Added a Cancel button to the Deployment Status screen that allows deployment operations to be cancelled.
26. Altered the Deployment Status screen such that all object/deployment-target combinations are populated into the list prior to deployment.  Thereafter, as each object is being deployed an icon is displayed to indicate that the object is being deployed.  Additionally, an execution timer displays the current execution time for each object being deployed.
27. Object definitions now exclude square-bracket identifiers if the option is not enabled and the object does not have spaces in it.  However, square-bracket identifiers are still used in storing the object and for the purpose of comparisons and deployments.

Bug Fixes:

1. Fixed a bug where objects whose owner was not “dbo” would fail to save.
2. When checking out multiple objects, only the first object in the selected list would have the “Checked Out By” field updated.
3. When working within the Object Comparer, any objects that were checked in were not having the “Checked Out By” field reset to blank.
4. When viewing an object in Read Only mode, it was possible to check out that object even if the object was checked out by another user.
5. When adding a new database to a project and attempting to specify which objects to add, the Triggers check box was not checked as it should have been.
6. In the Object Comparer, if one of the check boxes in the Select area was checked, selecting another object list would maintain the state of all check boxes.
7. When viewing object references the connection to the database was made using a trusted connection, which would not always be valid.
8. Fixed a bug where changes to the SET statements preceding and following an object’s definition would incorrectly flag the object has having changed outside of SQLDBcontrol.
9. Creating objects with an owner other than “dbo” would fail.
10. When opening a summary list of Objects from the Project Explorer or Object Comparer and mouse over the very first object in the list, the tooltip would not appear unless the mouse was moved over the object below it.
11. When deleting objects from multiple databases the progress bar incorrectly displayed the progress and it was also possible for the operation to complete but the Ok button would not become visible.
12. When declaring multiple variables with the same DECLARE statement, only the first declared variable would appear in subsequent IntelliSense lists.
13. In some circumstances, sending exception information would result in an error.
14. When sorting by the “Last Updated” column an exception would occur if there were blank values in that column.
15. When reporting errors in T-SQL statements that were executed, the line number shown would be incorrect if multiple batches were run as part of the execution statement.
16. Fixed rare bug where running a select statement that returned encrypted unicode data occasionally caused the application to hang.
17. Fixed a bug where, if the first character in an editor was a space an exception would be raised.
18. Fixed a bug where it was possible to check out a deleted objected when viewing the object’s definition.
19. When deploying a trigger to a database that already contained a trigger of the same name, the existing trigger was not dropped and an error occurred when deploying the trigger.

---

SQLDBcontrol Support

support@sqldbcontrol.com