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.3.
- Aginity Workbench is now compatible with Netezza Platform Software (NPS) version 7.1.
- A new look of Aginity Workbench. The new UI features a left-hand side bar, which contains buttons (tabs) for currently open application components, such as Query Analyzer and the Compare Schemas tool. By clicking the buttons in the side bar, you can switch between the open windows. Another change is that new icons are used throughout. Additionally, the toolbars are now available with larger icons to make it easier to distinguish between the buttons.
- Support for VARARGS stored procedures.
- A Secure File Transfer Protocol (SFTP) file explorer is now available in Workbench.
- An option was added to the Query Options window to keep a connection open and reuse it between query executions.
- An option was added to the Database Connection dialog box to allow SSL connections to a Netezza server.
- Improved import of specific SQL Server data types into Netezza.
- Ability to specify a table schema during import or export.
- An option was added to control the color of tab labels for users of the Windows Classic scheme.
- An option was added to allow users to choose to continue query execution even if a statement fails.
This section contains details of specific functions and changes that are included in Aginity Workbench 4.3.
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 NPS 7.0.2-7.1.
- 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
|4870||4.2||Users can now work with versions 4.0 and 4.1 of the Customer Insight for Retail plugin in Aginity Workbench.|
|4926||4.2||A user can choose to not install a new update of Workbench and not be prompted about availability of the update.|
|6138||4.3||Users now have the option of viewing the application window in full screen mode.|
|5183||4.3||The Type column in the Output tab grid now has a fixed width to prevent the column from automatically resizing during query execution.|
|5121||4.3||An option was added to the Database Connections dialog box to allow SSL connections to a Netezza server.|
Bug Fixes in Build 4.3.1864
|Severity||Reference||Description||Existed Since Version||Resolution|
|Major||1858||Primary and foreign keys are missing from a delta script generated by the Compare Schemas tool.||4.2||Fixed.|
|Major||5323||A foreign key is declared before the referenced primary key in an Alter script generated from the Compare Schemas tool in Workbench.||4.2||Fixed.|
|Major||5333||A delta script generated by the Compare Schemas tool does not contain ALTER OWNER statements.||4.2||Fixed.|
|Major||5324||Column comments are not compared in the Compare Schemas tool in Aginity Workbench.||4.2||Fixed.|
|Major||5966||"O.SCHEMA" not found" error when connecting Aginity Workbench to Netezza 188.8.131.52.||4.2||Fixed.|
|Major||5620||"Loading data from the database" and "loading data from the file" errors when a user compares schemas using the Compare Schemas tool in Aginity Workbench.||4.2||Fixed.|
|Major||6626||Data Import Wizard fails to correctly recognize the number of columns in an Excel file being imported.||4.3||Fixed.|
|Major||6447||The font colors set in Window personalization settings are not applied to query tab labels in Query Analyzer.||4.3||Options for specifying tab colors were added to the application options.|
|Moderate||4346||The Show Tables Size capability incorrectly refreshes the database information when a user selects a different database in the Table Space window.||4.1||Fixed.|
|Moderate||5623||Workbench crashes when a period is typed immediately after a table alias.||4.2||Fixed.|
|Moderate||6385||Expanding a table's column list in Object Browser is slower than in previous versions of Workbench.||4.2||The time it takes to expand a column list in Object Browser was reduced.|
|Moderate||6968||Ability to specify a schema during export of data from a table.||4.3||Fixed.|
|Moderate||6836||When a user selects the "Generate to existing Query Analyzer window" option in the Script Database window to generate DDL for a table that was created from an incorrect explicit cast to decimal, a message "The DDL has been generated successfully" is displayed although an appropriate error message should be displayed instead.||4.3||Fixed.|
|Moderate||6446||Workbench generates an error when a query ends with a semicolon (;) or two hyphens (--), and contains a parameter.||4.3||Fixed.|
|Moderate||6393||Unable to import a file that contains a column with negative values if the column's data type is defined incorrectly.||4.3||Fixed.|
|Moderate||6388||Data is incorrectly imported from an Excel file if a worksheet other than the first one is selected for import in the file.||4.3||Fixed.|
|Moderate||6817||When attempting to use the SPU Utilization Monitor, a warning may occur indicating “Invalid connection string attribute.” The query still runs and the plan is obtained, but there is nothing in the SPU utilization section.||4.3||Fixed.|
|Minor||5334||Some fields having the same values are highlighted in the Compare Schemas tool.||4.2||Fixed.|
|Minor||1606||Scripts generated by the Compare Schemas tool in Workbench prefixes procedure names with schema names in all DROP statements, which causes Netezza to generate an exception.||4.2||Fixed.|
|Major||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||6627||When importing data that includes dates from Excel using the Data Import Wizard, 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.|
|Major||7747||During import from an external Oracle, Teradata, or MS SQL Server database, a user attempts to save a specified user name and password in the Connect to Database dialog box, but the provided credentials are reset to the default values for that type of database. As a result, the user cannot connect to the database.||Enter the appropriate user name and password in the Connect to Database dialog box to connect to the database—without saving the credentials.|
|Moderate||766||The order of objects in Object Explorer incorrect if the list contains both case-sensitive and case-insensitive object names and Quoted Identifier is unchecked.||N/A|
|Moderate||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||2951||You cannot use an expression that evaluates to a date as a DATE parameter.||Insert the desired expression “As-Is”.|
|Moderate||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||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||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||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||7280||When attempting to execute DDL to the script window for a table, an error message is displayed when the table being used was not present (it had been deleted) and the table metadata had not been refreshed. The error message itself, reading “Unable to object a list of columns for a table. It might be deleted or you might not have enough permissions.” does not make the suggestion to refresh the table listing.||Refresh the table metadata.|
|Moderate||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||5973||You cannot import from views when using the remote database import from Microsoft SQL.||N/A|
|Minor||4090||If you begin a download using an explorer (such as SFTP or HDFS) and abort the download, a small portion of the file remains on your target system.||Manually delete the file on your target system.|
|Minor||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||7285||During a SELECT statement, dates in the format “01-01-01” cause the error “One of the identified items was in an invalid format.”||Use a WHERE clause to eliminate invalid rows or cast the date as VARCHAR.|
|Minor||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||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.|