Aginity Workbench for PureData System for Analytics 4.5 Release Notes

Aginity Workbench for PureData System for Analytics provides new functionality and improvements in stability and quality of the software over previous versions. These release notes summarize the new features and changes that apply to version 4.5.

What's New? (Also See Full List of Changes)

This section provides information about the main new features in version 4.5.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench 4.5.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, select Install this update now to download and install the update.

You can also choose to postpone installation of the update until the next time you run Workbench or suppress the update alert.

You can also check for updates manually by clicking Check for Updates on the Help menu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested against NPS versions 7.1.0.2-P2 and 7.2.0.3-P2 [Build 43166].

System Requirements

  • Windows XP or later
  • Windows Installer 3.1
  • .NET Framework 3.5 SP1
  • ODBC (recommended) or OleDB driver. (Drivers must be 64-bit for 64-bit Windows or 32-bit for 32-bit Windows.)
  • Memory: 256 MB RAM
  • Disk space: 100 MB, plus any necessary space for .NET Framework and Windows Installer

Full List of Changes Since Aginity Workbench 4.4

New Features

Reference Summary
WPD-187 Database object search is available.
WPD-445 You can export and import code snippets.
WPD-429 During import of a large file, as well as having the first 1,000 rows in the file analyzed by default, you can choose to analyze more rows.
WPD-127 During import, you have additional options to specify what to do with an existing destination table.
WPD-173 You can create entity filters for Fluid Query data sources.
WPD-183 You can display parameter information in a tooltip for a stored procedure or function after typing an opening parenthesis after its name.
WPD-184 You can display a tooltip providing information on a database object when you point to its name on a Query Editor tab.
WPD-185 You can split the Query Editor using one of the following options:
  • Single pane
  • Horizontal split
  • Vertical split
  • Four-way split
WPD-186 If you use multiple monitors, you can move the Query Analyzer window to one of them.

Bug Fixes in Build 4.5.0.2319

Severity Reference Description Existed Since Version Resolution
Major WPD-419 The Database Grooming window shows the wrong schema for selected tables, which causes the database grooming operation to fail. 4.4 Fixed.
Major WPD-404 Workbench automatically places quotation marks around a schema name with a non-SQL character in the SET PATH statement within a query, which causes the query to fail with the error "Error setting current path." 4.4 Fixed. The automatic enclosing of schema names in code is removed.
Major WPD-342 Tables are not showing in Big SQL Fluid Query data sources in Query Analyzer. 4.4 Fixed.
Major WPD-371 When a user closes the Job Monitor, it incorrectly attempts to close the main Workbench window. 4.4 Fixed.
Moderate WPD-422 The More Logs option (allows access to additional log files) in Job Monitor is unavailable during import of a .csv file. 4.4 Fixed.
Moderate WPD-402 Sometimes Workbench fails to install updates. 4.4 Fixed.
Moderate WPD-383 An attempt to read zone maps from a table fails on Netezza that has implicit cross joins disallowed. 4.4 Fixed.

Known Issues in Build 4.5.0.2319

Severity Reference Description Workaround
Major WPD-512 The Aginity CIA plugin is not compatible with Aginity Workbench version 4.5. If you need to use the CIA plugin, make sure that you use the latest compatible version of Aginity Workbench (4.4.2193), which you can download from the Aginity Workbench for PureData System for Analytics Downloads page.
Major APD-5627 When importing DB2 tables from an external database, an error may occur indicating that Length cannot be less than zero. Install the DB2 client on the client machine so you can successfully connect to a DB2 database.
Major APD-6627 When importing data that includes dates from Excel using the Data Import Wizard, the Data Import Wizard fails to properly identify dates automatically and fails to load dates when manually configured to do so. Set the column in Excel to text instead of date so you can load the data.
Moderate APD-766 The order of objects in Object Explorer is incorrect if the list contains both case-sensitive and case-insensitive object names and Quoted Identifier is unchecked. N/A
Moderate APD-1939 A DDL (delta) script generated by the Compare Schemas tool fails with an error if the same table in the source and target schemas contains a foreign key to different tables.  The error occurs because when applying the foreign-key update to the target schema, the script first drops the old referenced table in the target schema and then attempts to drop the foreign key to the previously dropped table. Choose one of the following two workarounds, depending on whether you prefer to generate one or two delta scripts.

Workaround 1: Generate one delta script

  1. Open the source and target schemas in the Compare Schemas window.
  2. Click the appropriate Alter Script button to initiate script generation.
  3. In the Generate Delta Script Options window, under Entities to Script, select the Drop these entities check box and select appropriate check boxes under Create these entities and Modify these entities.
  4. Save the generated script to a file.
  5. Locate the DROP TABLE statements within the script and move them to the end.

    This will ensure that the foreign key is dropped before the old referenced table.

  6. Run the script against the target schema.

Workaround 2: Generate two delta scripts

  1. Open the source and target schemas in the Compare Schemas window.
  2. Click the appropriate Alter Script button to initiate script generation.
  3. In the Generate Delta Script Options window, under Entities to Script, clear the Drop these entities check box to not drop any tables, and select appropriate check boxes under Create these entities and Modify these entities.
  4. Save the generated script to a file.
  5. Generate a delta script for the schemas again, selecting the Drop these entities check box this time.
  6. Save the script to another file.
  7. First run the script file created in step 4 and then the one created in step 6.
Moderate APD-6590 When attempting to save a modified query set that was opened from a read-only file, the save does not work, but no error is given indicating why you could not save. Ensure you have write permissions to the query set file before saving.
Moderate APD-6633 When working with multiple schemas with views and tables that have the same name, the population of fields in the drop-down list does not respect the default schema selection. Avoid using the drop-down list when working with multiple schemas with duplicated view/table names.
Moderate APD-6835 When selecting vertical blocks of text (as opposed to full lines) and using the Make selection UPPER/lower case function, the selected text is shifted vertically. Manually adjust the lines.
Moderate APD-7121 If you have different connections open in two different tabs, if you close one of the tabs, toolbar buttons in the remaining tab disappear other than the Connect button. Open another connection to restore the buttons.
Moderate APD-5471 Installation of Workbench on Microsoft Server 2012 fails on the prerequisites. Do a "Add Features" for .NET 3.5 (which includes 2.0) in the Server Manager.
Moderate APD-5973 You cannot import from views when using the remote database import from Microsoft SQL. N/A
Minor APD-6163 In Standard mode in the Output area, some SQL statements are inadvertently omitted. However, they are correctly displayed in Grid mode. N/A
Minor APD-5972 The Connect to Microsoft SQL Server screen has a background graphic that is misaligned with the text and controls on the screen. Functionality is not affected. N/A
Trivial APD-3711 When the field type is Date, the year 0 (for example, 0000-01-01) causes an error “Year, Month, and Day parameters describe an un-representable DateTime.” Either cast the date as a VARCHAR or do not use the year 0.
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.

** Aginity, Inc.’s Provision of Scripts and Similar Materials at Help Desk Center. For the convenience of Aginity Amp™ clients, we provide code snippets, scripts and similar materials at this Help Desk Center. Such materials are reference materials provided for illustration purposes only. These are intended to serve as an example for self-service clients and are generally geared to respond to common questions asked by similar clients. Such materials constitute Aginity’s intellectual property. Aginity Amp clients and their authorized users are permitted to use these materials in connection with their software license and/or subscription of Aginity Amp. Nothing herein shall limit Aginity’s right to use, develop, enhance, modify or market any of these materials as part of its business. These materials are not formally supported by Aginity or its affiliates. Usage of these materials does not guarantee any specific results, uptime, performance or error-free operation. Aginity disclaims all warranties of any kind, whether express, implied, statutory or otherwise, including any implied warranty of merchantability or fitness for a particular purpose.

Powered by Zendesk