These release notes summarize the features and bug fixes that apply to Aginity Workbench for Redshift version 4.3.
- Integration with Amazon’s Simple Storage Service (S3 buckets) affords importing and movement of data via S3.
- The UI of Aginity Workbench 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. Additionally, the toolbars are available with larger icons to make it easier to distinguish between the buttons.
- Support of Redshift-specific keywords.
- Visualization (via a stacked bar chart) of overall query execution times and execution time by individual query segment. This provides easy visibility into how your queries are using all your processing nodes and slices to find bottlenecks and optimize.
- An option in the Query Options window for keeping a connection open and reusing it between query executions.
- An option in the Database Connection dialog box enables SSL connections to a Redshift server.
- Users of the Windows Classic scheme can specify the color of tab labels.
- Users can choose to continue query execution even if a statement fails.
Upgrading from Prior Versions
- Uninstall the previous Beta version of Aginity Workbench for Redshift.
- Download and install version 4.3 from the Aginity Workbench for Redshift Downloads page.
- Windows XP or later
- Windows Installer 3.1
- .NET Framework 3.5 SP1
- Memory: 256 MB RAM
- Disk space: 100 MB, plus any necessary space for .NET Framework and Windows Installer
|336||4.3||An option for keeping connection open between executions.|
|6844||4.3||An option for ignoring SQL errors.|
|3776||4.3||As a Redshift WB user I want quick and easy access to query processing details.|
|5183||4.3||The Type column in the Output tab grid has a fixed width to prevent the column from automatically resizing during query execution.|
|5121||4.3||An option in the Database Connections dialog box to allow SSL connections to a Redshift server.|
Bug Fixes in Build 4.3.1962
|Moderate||7129||Leading zeros in VARCHAR values are lost after export to Excel.||Fixed.|
|Moderate||8090||When trying to execute an Explain SQL statement for a query from the server-side query history, a user gets an error.||Fixed.|
|Minor||4021||Failure to copy files from the S3 file explorer to a local machine using a drag-and-drop operation.||Fixed.|
|Minor||4022||Cannot drag and drop files from a local machine to the S3 file explorer.||Fixed.|
|Moderate||4093||Import of a file from the S3 file explorer fails because invalid data types are set for the columns in the file.||Set all column data types as VARCHAR and re-import the file.|
|Moderate||3788||The Abort feature in Redshift Workbench does not terminate a query that is currently running.||Use the SQL at http://docs.aws.amazon.com/redshift/latest/dg/r_CANCEL.html to find the process ID of the running query and cancel it.|
|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||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||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.|