Welcome to SQLDBcontrol Forums Sign in | Join | Help
in

Maintenance release 1.3 is available for SQLDBcontrol

Last post 08-25-2006, 10:46 by admin. 0 replies.
Sort Posts: Previous Next
  •  08-25-2006, 10:46 46

    Maintenance release 1.3 is available for SQLDBcontrol

    A maintenance release containing some feature additions and minor bug fixes is now available.  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.

     

    SQLDBControl

    Release 1.3.00000

    25 Aug 2006

     

    -------------------------------------------------------

     

    Feature Additions:

    1. Provided support for adding T-SQL scripts into source control, which can also be deployed* as with other objects.  Unlike other objects, T-SQL scripts are not applied directly to the SQL Server when checking in.
    2. Added context menu option to get latest from within an object editor when an object is being edited.

     

    Code Changes: 

    1. When getting the latest definition for objects that are checked out the user is now asked to confirm that they want to get the latest and risk losing any changes.  If the object is checked in, the latest definition is applied and a history item is created.
    2. When executing a query whose results are output to text the cursor now remains in the query editor window as opposed to the results window. 

    Bug Fixes: 

    1. When editing triggers it was possible to click on the Permissions button.
    2. When editing objects, under certain circumstances, an old check box control would become visible, this is now redundant.
    3. When viewing object references, if there was an object reference at the very end of the document, an out of memory exception could occur.
    4. When recovering a deleted object, if the object still existed on the SQL Server the SQL Server object definition was not being overwritten with the recovered object.
    5. Double-clicking on an empty part of the Object Summary List would cause an exception.
    6.  When checking in an object that is newly created an exception would occur if the object was not saved initially.


    * Does not apply to SQLDBcontrol Express.


    SQLDBcontrol Support

    support@sqldbcontrol.com
View as RSS news feed in XML
Powered by Community Server, by Telligent Systems