The new Key Assist tool allows a user to quickly lookup an action and find the corresponding key binding. When accessing key bindings, the user may press Help->Key Assist from the menu, or the corresponding hot key which will popup a dialog containing a list of categories, actions and corresponding key bindings. The dialog contains a quick filter which allows the user to quickly isolate the exact action he/she is looking for. The user may also quickly access the configurable key bindings in case he/she wants to edit the current key binding for any action by clicking on the "Edit Keys" button.

Documentation: Keymapping Assistant

Multiple Application Windows

Docking Framework

The new Docking Framework allows elements of the application frame to be docked and undocked. It means that the user can shrink, expand and relocate application panels to match his/her preferences.

The new Multiple Application Windows action allows the user to launch another frame of Aqua Data Studio without launching another instance of the application. Sometimes it is convenient to have multiple frames of Aqua Data Studio running so simultaneous work with different databases can be decoupled. Now multiple application windows of Aqua Data Studio can be run from a single application instance.

Documentation: Docking Framework and Multiple Application Windows

The new Browser Details View allows users to see the details of object groups from the schema or script browser in a dockable window. When a folder with objects is selected, their details are represented as a table. For example, it allows users to check offline or online status of several databases at the same time, to see what processes are running or to view what constraints are currently disabled.

Documentation: Details View

Added File->Options:General:Appearance:[Display Splash Screen] to give a user an option to enable/disable the splash screen for the application start.

Documentation: Options

Now, when a file in the Schema/Script Browser is double clicked, the correct editor (Text, SQL, HTML, XML) for that filetype opens the double-clicked file in a new tab.

Documentation: Schema Browser

Now, has the ability to create folders from a popup menu. Also allows drag and drop of mount points from folder to folder for organizing mounts.

Documentation: Schema Browser

Now, SQL scripts may be executed from the commandline without launching the Aqua Data Studio GUI. This allows scheduling the execution of scripts from an OS scheduler such as a Unix cron job or with Windows Task Scheduler. Cron jobs or scheduled tasks may be created to generate pivot charts and graphs and email the saved results without direct user interaction per month, day, hour or as the user desires.

Documentation: Command Line

Grid Aggregate Functions allow users to calculate Count, Count Numbers, Sum, Min, Max, Average, and Standard Deviation functions on the grid data highlighted, in the same fashion as it's done in popular spreadsheet applications. This new feature is enabled in the Table Data Editor, Query Window Grid Results and Query Builder Grid Results.

Documentation: Grid and Pivot Functions

Save Results can be previewed by clicking on the Preview Script tab, displaying the Aqua Command for the current Save Results As options.

Documentation: Save Results

Autocompletion for SQL Server, Sybase, MySQL and Informix now has support for completion accross databases. Indicating a table which is in a database other then the current database will now provide column completion for the correct table. Autocompleting for tables in databases other then the current one will also complete correctly. Here are some examples:

Current Database: master

Query: select * from Northwind.dbo.^Customers cu left join Example_Data.dbo.^Employees e on cu.^CustomerID = e.^EmployeeID

Completion in the locations marked with "^" will complete with the appropriate tables for the database, or the appropriate columns for the matching table

Documentation: Cross Database Autocompletion

The new Global Auto Completion Cache provides an option to allow the sharing of Auto Completion schema data across different query windows. With this new option enabled, if you open 10 query windows for one registered database server, the Auto Completion schema will be stored only once and shared across all the query windows.

Documentation: Global Auto Completion Cache

File->Options->Scripts-> now has options "Quote Identifier for Object Table Completion" and "Quote Identifier for Column Table Completion" which will allow auto-completion to complete object/column names to be quoted on completion.

Documentation: Quote Identifier

Now, the Query Analyzer popup menu includes new options Execute, Execute Current, Execute Edit, Execute Explain Format Script, Format Current Statement, Morph to Delimited List, Comment Statement, Comment Line and Uncomment. It allows a user to execute the commands from the popup menu.

Documentation: Query Analyzer Popup Menu

Query Analyzer scripts now have support for new client side commands '.saveResults' and '.saveLastResult' which allow a user to either save query results into an EXCEL, HTML, XML or CSV document or to insert the results into a table. The '.saveResults' command saves the results of all of the queries in the window while the '.saveLastResult' command only saves the results of the last query. The commands include saving of the result charts and grids if present.

There are also supporting commands '.setResultSettings' that allows configuration of the results and '.setPivotResultSettings' that allows configuration of the pivot results.

Example:

.saveResults 'Format=EXCEL,Source=PIVOT,File="c:\\mypivot.xls",IncludeSQL=false, IncludeHeader=true, IncludeRowCount=true, IncludeNullText=false, AlternateRow=false,Overwrite=true'

Documentation: Aqua Commands

A new automate feature has been added under the Automate menu: Automate->Morph To Delimited List. This allows the user to convert a block of text into a delimited list with the appropriate options. Simply highlight a block of text in the editor and choose "Morph To Delimited List." This will prompt the user for different options about the source block, and the destination block of text, with the result destination overwriting the source block of text. This allows the user to paste text from the Grid Results, Excel or other applications into the editor and then convert them into a comma delimited list or any delimited list which may then be used for completing a query or other documentation.

• Source
  
  • Initial Delimiter - Identifies the item delimiter in the original selected block of text so Aqua Data Studio may parse the text.
  • Include line feeds as a delimiter - Identifies whether Aqua Data Studio should recognize a line feed as a delimiter in addition to the initial delimiter.

• Destination
  
  • Resulting Delimiter - The delimiter that will be used when generating the resulting block of text.
  • String quoted identifier - The quote identifier for each item in the list if needed.
  • Wrap Line at Column - Determines whether the resulting text should be wrapped and at what column count to wrap.

Documentation: Morph to Delimited List

The SQL History now allows you to automatically archive SQL statements that are removed from the SQL History when the number of queries exceeds the defined maximum number. This option can be turned on and off, and an archive folder can be selected by a user in File->Options:General:History. Queries from SQL History may also be selected, manually moved and saved in SQL History Archive. A tab has been added to the SQL History window which allows a user to search through the archive by keyword and date, and present search results as a table which is similar to the current SQL History tab. The last selected search parameters are persistent across multiple runs of the application. If a search takes an extended period of time, a progress monitor pops up showing the operation progress.

Diagram of how SQL History can be used for Audit Trail and SQL Query Analysis. SQL History Archives can be parsed and stored in a database for keeping a full audit trail of who did what on the database at what time. This can be valuable including for Sarbanes-Oxley compliance or any other regulatory requirements.

Documentation: SQL History

Object Search allows users to search for database objects and filter with a number of selectors including Object Names, Column Names, Index Names, Constraint Columns, Trigger Columns, Procedure Code, Trigger Source and View Source. Also, there is an option to include or exclude System Objects. Next to the "Search" button there is an "Append" button to let the user search without clearing the previous results. Once results are generated, they can be sorted by Object Name, Object Type, Parent and Owner. These results can be refined further through the Quick Filter.

Added support for Permissions: Script Generator tool now has an option to include object permissions into the DDL of the object being scripted. This option can be turned on and off by a user in the Script Generator tool dialog.

For DB2 added an option to enable/disable using specific procedure names as file names when saving procedure scripts into individual files. As DB2 can have multiple procedures with the same name, specific file names should be used together with real procedure names when naming individual script files. However, if a user is sure that there are no procedures with the same name being scripted, then he/she can use real procedure names and disable the option.

New Server Script Generator allows a user to generate SQL scripts for server objects such as databases, users, roles, alerts, jobs, tablespaces etc. This tool works in the fashion similar to Schema Script Generator. In the Server Script Generator dialog, General tab the user can pick server object types to be scripted and select object names from a list of objects. After clicking on the "Next" button, the user can proceed to the Options tab to select scripting options. There the user can specify whether he/she wants to save the scripts in a single file, in multiple files or to view them in the preview tab. The scripts will be generated after the user clicks on the "Next" button.

• Sortable Columns: If a user clicks on a header of a column, or the headers of multiple columns, values can be sorted by ascending or descending order. Simultaneous multiple column sorting is available if the user keeps the Ctrl key pressed while selecting column headers.
• Filterable Rows: Quick filter field is available at the right top corner to help the user filter and view desired column values. If the user clears changes which were in the filter so that the rows are no longer in the filter, the view stays the same for users convenience until a new filter is applied.
• Multi-Table Editing: Table Data Editor now allows the user to insert an empty row not only at the table end, as was the earlier case, but before and after any row in the table. Cloned rows are now inserted directly after the row being cloned.
  Limitations
  1. Columns with the same name belonging to different tables are not editable as the table they belong to cannot be identified.
  2. Insert, clone and delete row operations are not available in the multitable mode as they can't distinguish between the tables.
  
• Insert Row Before & After: Table Data Editor now allows the user to insert an empty row not only at the table end, as was the earlier case, but before and after any row in the table. Cloned rows are now inserted directly after the row being cloned. If the corresponding columns are sorted, the view stays the same until new sorting is applied.
• Status Bar: If data loading takes an extended period of time, now a progress bar pops up to show that the operation is in progress.
• Option to save queries to SQL History: This option can be enabled/disabled in File->Options[Table Editor]. When the option is enabled, queries generated in Table Data Editor are saved to SQL History after being executed and commited. With the Full (default) transaction type all of the queries are saved as one entry, otherwise queries are saved by batches being commited. If a query or a batch fails, including the case when a user cancels it, further queries are not executed and not saved.
• Options->Permissions->Table Data Editor: Allow Primary Key definition changes: A new option that determines whether Primary Key definitions can be changed for servers.

The Query Builder now also has support for Pivot Results, Grid Charts and Pivot Charts.

Added a tab presenting the results as a pivot grid, i.e. as a set of pivot grids. The number of pivot grids corresponds to the number of result sets obtained when running the query. The pivot grids are displayed on a multi-level splitpane providing full control over sizes and configurations of each pivot grid. Grid configuration is persistent over multiple runs of the same query in the same query panel, i.e., if a user configures a pivot grid and then re-runs the same query, this pivot grid will maintain its configuration. The option to display pivot grids can be turned on and off on the toolbar as well as from the Query menu.

Pivot grid configurations can be saved as XML layouts and those layouts can be loaded back into existing pivot grids. Pivot grids allow the grouping and summarizing of selected columns and rows of data to obtain a desired report. They are particulary useful with large amounts of data, helping a user to classify data by categories and obtain summaries without the time consuming search it would normally take to look through all of the data.

The Grid and Pivot Grid tabs now allow the user to graph out data from the resulting data set and represent it as a Grid Chart and Pivot Chart for convenience of data viewing and interpretation.

Documentation: Pivot Grid & Graphs

Option to save queries to SQL History: This option can be enabled/disabled in File->Options[Table Editor]. When the option is enabled, queries generated in Query Builder are saved to SQL History after being executed and commited. With the Full (default) transaction type all of the queries are saved as one entry, otherwise queries are saved by batches being commited. If a query or a batch fails, including the case when a user cancels it, further queries are not executed and not saved.

Documentation: Query Builder SQL History

The Export Tool now has an option to indicate the Date quote identifier for the output results.

The new Results Compare Tool provides a user with a graphical representation depicting comparisons between two result sets obtained from either the same query or two different queries. It is displayed as a table presenting differences in both data structure and data, allowing a user to see what columns and rows have been added or deleted and what cells have been edited in the second result set compared to the first result set. Users select a primary key from the Primary Key tab to compare rows. The result sets are obtained from the query analyzer panel results, including all of the query analyzer tabs open, and a user is prompted to select two result sets from a dialog. The results comparison is refreshed when a user changes the choice of primary keys. It also may be refreshed using the Refresh button. In the latter case a user is prompted to select two new result sets from a dialog, and the results comparison is loaded into the same Results Compare panel. As the results comparison is being calculated, the progress of the calculation is shown on a progress bar.

Limitations: If a query returns multiple rows with the same primary keys, then there is no reliable way to identify modified rows in the result sets. Multiple rows for the same primary keys are obtained in 2 cases: due to user selection of the primary keys and to the selection of the query columns. Initially, Results Compare is run with all of the common columns selected as primary keys. In this case, if the query returns duplicate rows, it's due to query column selection. If a table has duplicate rows and no primary key defined, then there is no way to determine if those rows have been modified even though a user selects all of the table columns for the query and all of the common columns as primary keys. If this problem occurs, Results Compare is still run on the result sets using intelligent assumptions about what rows correspond to each other, but a user is warned about duplicate rows. If there are duplicate rows in the result sets on the initial run, then a user is advised to change column selection in the query. If there are duplicate rows obtained after a user changes the set of primary keys, then the user is advised to redefine the primary keys.

The Schema Compare Tool has many new enhancements that provide more detailed information including the ability to save the results. Below is a list of new features included in the Schema Compare Tool:

• Object Permissions: Support for permissions in the comparing of objects. In the options, the user may now choose to include permissions in the DDL of each object to be used in the comparing of the objects.
• Background Processing: The progress dialog has now moved to the panel view of the comparing so the user may continue working on other tasks while the Compare Tool continues to work.
• Refresh: A "Refresh" button has been added to the toolbar allowing the user to re-query for the object definitions in the database in case any changes to the schema have taken place.
• Data Compare: A "Data Compare" button has been added to the toolbar to allow the user to compare the data in the currently selected table.
• Save As HTML: The toolbar now contains a "Save As HTML" button that allows the user to save the Compare results to HTML so that they may be saved and emailed to other users. The "Save" provides the user different options such as layout, font, file name and the object choices.
• Preview in Browser: The toolbar now contains a "Preview in Browser" button that allows the user to preview the last saved Compare results to quickly access the saved HTML.
• Compare Count: The object results now contains a column indicating the number of Compares between the two matching objects.

The Directory Compare Tool has many new enhancements that provide more detailed information including the ability to save the results. Below is a list of those features:

• Filtering by File Size: The Compare in file sizes can now be filtered and included in the Compare.
• Background Processing: The progress dialog has now moved to the panel view of the comparing so the user may work on other tasks while the Compare Tool continues to process.
• Refresh: A "Refresh" button has been added to the toolbar allowing the user to requery for file or directory changes in case any changes to the filesystem have taken place.
• Compare Count: The file and directory results now contain a column indicating the number of Compares between the two matching objects.
• File Size: The file and directory results now contain two columns indicating the Compare of each matching file.
• Save As HTML: The toolbar now contains a "Save As HTML" button that allows the user to save the Compare results to HTML so that they may be saved and emailed to other users. The save provides the user different options such as layout, font, file name and the object choices.
• Preview in Browser: The toolbar now contains a "Preview in Browser" button that allows the user to preview the last saved Compare results to quickly access the saved HTML.

The File Compare Tool has many new enhancements that provide more detailed information including the ability to save the results. Below is a list of those features:

• Refresh: A "Refresh" button has been added to the toolbar allowing the user to requery for file changes in case any changes to the files have taken place.
• Save As HTML: The toolbar now contains a "Save As HTML" button that allows the user to save the Compare results to HTML so that they may be saved and emailed to other users. The "Save" provides the user different options such as layout, font, file name and the object choices.
• Preview in Browser: The toolbar now contains a "Preview in Browser" button that allows the user to preview the last saved Compare results to quickly access the saved HTML.
• Drag & Drop of files into tool: A user now can directly pick up a file from a file manager, as well as from the Script Browser and Scripts folder in ADS, and drag & drop it into the text field instead of browsing for the file. The file text will get displayed in the text field and the file Compare will be calculated.

For Sybase Anywhere added support to script CREATE & DROP Events

For Oracle added support to script CREATE & DROP for Database Links

The new Sybase SQL Debugger has been designed to help with testing and debugging of SQL functions and procedures for Sybase ASE. Its debugging features include:

• Setting a break point in the function or procedure body. A user can set a break point at any line in the function or procedure source code in order to run it up to this line. The breakpoints can be viewed in the Breakpoints tab.
• Running the function or procedure up to the break point with parameters provided by the user. The execution can be stopped at any time using the stop button. Ouput messages for the execution can be viewed in the Console tab.
• "Step Over" button allows the user to move to the next line of the code.
• The user can enter variables and view their values during the execution in the Variables tab.
• The user can enter expressions and watch their values in the Watches tab.

Documentation: Sybase Debugger

The new Oracle SQL Debugger has been designed to help with testing and debugging of SQL functions and procedures for Oracle. Its debugging features include:

• Setting a break point in the function or procedure body. A user can set a break point at any line in the function or procedure source code in order to run it up to this line. The breakpoints can be viewed in the Breakpoints tab.
• Running the function or procedure up to the break point with parameters provided by the user. The execution can be stopped at any time using the stop button. Ouput messages for the execution can be viewed in the Console tab.
• "Step Over" button allows the user to move to the next line of the code.
• The user can enter variables and view their values during the execution in the Variables tab.
• The user can enter expressions and watch their values in the Watches tab.

Documentation: Oracle Debugger

The Session Manager, Storage Manager and Security Manager now have a quick filter for TreeTable list item tabs.

The Session Manager now has an option to color syntax of sessions by status, making it easy to identify sessions which are being blocked or are blocking based on lock conditions.

The Instance Manager now has a Jobs tab for Oracle 10g and above that allows viewing, creating, altering, dropping, starting and stopping of jobs using the DBMS_SCHEDULER package.

Documentation: Oracle DBA Tools

Documentation: Sybase DBA Tools

Documentation: MS SQL Server DBA Tools