These release notes summarize the changes in Aginity Workbench for PureData System for Analytics version 4.9. The release notes also contain system requirements and list the known issues with the release.
What's New? (Also See Full List of Changes)
This section provides information about the main new features in version 4.9:
- You now have an application-level setting to specify whether to reuse an open target database connection between query executions.
- An option is now available to trim trailing spaces from strings in a file being imported.
- You can turn on a default entity filter to display only relevant database objects in the Object Browser each time you connect to a target database.
This section contains details of specific functions and changes that are included in Aginity Workbench 4.9.
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.
Aginity Workbench has been tested against Netezza Platform Software (NPS) versions 22.214.171.124-P2 and 126.96.36.199-P2 [Build 43166].
- 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
Bug Fixes in Build 188.8.131.524
|Severity||Reference||Description||Existed Since Version||Resolution|
|Major||WPD-568||Displaying a query plan for a query that includes the FuncJoinNode node causes an error.||4.5||Fixed. FuncJoinNode was added to the query plan.|
|Moderate||WPD-699||An error occurs when a user attempts to use the Compare Schemas feature.||4.6||Fixed. The feature now works as expected.|
|Minor||WPD-681||Using semicolons in subqueries causes Workbench to crash.||4.4||Fixed.|
|Minor||WPD-216||The Help menu contains an empty item under "Check for Updates" and a delimiter followed by no menu items under “Follow us ...”||4.4||Fixed.|
|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.|
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
Workaround 2: Generate two delta scripts
|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|
|Minor||WPD-631||When a user sets the Database drop-down list to a database with a name that is not in the catalog default case on the target system, and then attempts to run a query against the database, an error occurs.||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.|