Aginity FAQs

Background

Aginity script is a powerful utility that over time will be used to expose a lot of powerful features in Aginity Pro and Team. Currently, we have deployed the ability to use Aginity Script to export data to files.

This knowledge base article talks about making the export feature more useful when you use it in conjunction with the Aginity Catalog.

Step by Step Approach

1. Create two entries in your catalog to hold the code for exporting to files (before SQL query and after SQL query portions) as shown below.

2. Here is an example where Ive put this syntax in with the typical defaults I want to use and it will also prompt me when I run this to add a file name to this:

3.When you have a query you want to export, just type @{beg} and it should find the catalog reference you need before the query.

4. Do the same with @{end} after the query and you should end up with something like this in a couple keystrokes. When it runs, it will prompt you for a filename and spool out the results.

Recently Aginity released a series of SQL catalogs compatible with Aginity Pro and Team on Github. These catalogs are pre-built, ready to use queries against our most popular supported databases.

How do I get Started

Head right over to Github and read the How to Import documentation.

How do I Contribute

You have several options to help out.

Our GitHub repository is public so you can create a fork, create your own catalog, suggest modifications to ours, commit it, request a pull and well take if from there! Here is quick video on getting started with GitHub if you want to give this a try!

The easiest way is to send us an email at [email protected]. When you do this it will submit a ticket to us and we will take a look, ask/answer any questions and make sure the query gets put out in the community!

Finally, feel free to post packages directly to our community as well. We constantly monitor this site and if we like what you posted we will incorporate it into the repository!

Background

Within each Github repository youll find administrative, data engineering, analytic functions and analytic queries r eady to execute. Our goal with Aginity Pro and Team is to create efficiency in the SQL development community by promoting, sharing and reusing common queries and query patterns through our active catalog.

For example in the administrative catalogs we have prepared queries to do things such as dropping unused tables in a database. All of these queries interrogate the platforms data dictionary tables and will generate or execute the SQL scripts immediately. In our data engineering catalogs we may have scripts to help generate time and date dimension tables for analytic users to use to facilitate analysis. In our analytic catalogs we typically have executable examples that show you how to do complex things in SQL such as creating a linear regression analysis data.

Here is a sneak peak of some of the queries we have available:

Whats Next

Our support and services team continue to catalog queries, validate them and check them into the Github repository on a weekly basis. We are now ready to start engaging with our Pro and Team users to curate this catalog and work together as a community.

As we continue to learn how to best use the active catalog we allocate time to enable the community with our catalogs. Here are some of the areas we are focused on.

Analytic Functions

If you are like us you are constantly searching for SQL syntax or referencing SQL reference manuals. We are starting to catalog the most popular SQL functions that can be dragged into the query editor. The image below shows how we do this with the percentile_cont function in Redshift. On the left you can see the library of functions we put at your fingertips in the catalog.

Analytic Examples

Wecan'tanddon'twant to ship data back and forth so our goal is to write powerful SQL statements that you can easily translate to your data. Our analytic examples do just that. Shown below is a linear regression analysis that uses a catalog of SQL based math disconnected from the database. Provide the table names when prompted and youll be predicting growth or decline in whatever metric you choose to analyze!

Administrative Functions

Whether you are a DBA, data engineer or analyst you will be faced with the need to interrogate the data dictionary and will find yourself spending hours researching how to do this. We are packaging up the most functional queries and making them available to the community. One of my favorites shown below is the ability to generate drop table statements based on a table name pattern. As a data engineer I am always needing to keep my sandbox clean as I create data sets.

Data Engineering Functions

Lets say you want to aggregate your analytics up to a week and want to display a start date butdon'thave that handy date dimension laying around. Thats OK! We have a catalog query for that to use. The example below easily generates a time dimension. Just drag over the item and run the queries in sequence and voila, time date_dim!

In some cases you want to do a fresh install of Aginity Pro which includes removing the user files such as the catalog and your connections.

Warning: Catalog items and your connections will be removed when you do this.

On Windows

1. Using Windows "Add or Remove Programs" in Control Panel remove Aginity Pro.2.Go to Windows Explorer, navigate to C:/Users/<username>/AppData/Local/Aginity directory and rename aginity-pro to OLD-aginity-pro. This way we could recover the old version if you wanted. Remove it if you have no intention of using it again.3. Reinstall the product which should create a new version of the user files.

On Mac

1. Uninstall Aginity Pro by deleting it from your applications folder.2. Using Finder, navigate to ~/Library/Application Support/ and rename aginity-pro directory to something like OLD_aginity-pro. This way we can keep it if needed.3. Reinstall the product which should create a new version of the user files.

Recommendation

In version0.13.218 we released the Import/Export of your catalog items to a local file. We highly recommend you do this regularly as a backup strategy to ensure you don't lose any of your catalog items. Reference the production documentation on how to do this.

Background

We have had several tickets opened up since the release of Aginity Pro around the application crashing upon opening with a black screen which may look like this.

[email protected]

Typically you will get the Aginity Pro Splash screen then this black screen which in most cases says something like:

Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Database may be already in use: "Locked by another process: C:/Users/<username>/AppData/Local/Aginity/aginity-pro/aginity_pro.db.lock.db". Possible solutions: close all other connection(s); use the server mode [90020-199]

Root Cause

The transactional database underneath our application is being held onto by an existing process and causing the Aginity Pro process to not start. We think it is an Aginity Pro process that did not shut down properly but have been unable to recreate it in our lab, which is why we are asking for some help as well as putting in place safeguards to prevent this in our next release due out 9/16/19, but until then we wanted to ask for some help!

Identification and Work Around

First we are asking our community for some help on identifying the locking application! You can do this on Windows by doing the following.

Open up the the Resource Monitor (resmon.exe) application that comes with Windows as shown below.

Click on the CPU tab and then under Associated Handles search for "aginity_pro.db" as shown below

As you can see in this case an application prl_cc.exe is holding open the aginity_pro.db.lock.db as well as java.exe holding open aginity_pro.db.mv.db.

If you see this please kill both processes and try to reopen the Aginity Pro application and it should open without issue.

If you do see this please take a screenshot of the offending processes like the illustration above and send it to [email protected]. It will help us determine what is locking the file us or another application like anti-virus software.

In the example above java.exe is actually the Aginity Pro application which is a Java application and the lock file I opened in a text editor to simulate the locking behavior.

Typically, rebooting your machine should also release any locks.

On a Mac it is similar but done from Terminal. Open Terminal using Spotlight and typing "terminal" as shown below.

Once in a terminal issue the following two commands and take a screenshot or note the offending file locking the database under the COMMAND header in returned results.

1.lsof /Users/<Your Username>/Library/Application\ Support/aginity-pro/aginity_pro.db.mv.db

2.lsof /Users/<Your Username>/Library/Application\ Support/aginity-pro/aginity_pro.db.lock.db

The results of each command will look like this.

To kill the processes the best thing to do is reboot but if you desire to kill them manually you can issue the kill -9 command as shown below.

After killing the processes you should be able to restart Aginity Pro.

Please drop us a note at with the details of what you see!

Background

Over the past eight weeks we have seen several support cases where users of Aginity Pro on MacOS have had Pro crash upon opening. This occurs right after changing their password as dictated by their organizations Network Account Server rules. It appears that only Macs that use domain authentication are impacted by this.

We believe the root cause is a bug in MacOS itself where it is not preserving your passwords as expected when you attempt to update the Keychain password but instead it appears to regenerate a new Keystore thereby causing Aginity Pro to generate an new encryption key (as if it were a brand new install) that does not match the existing encrypted application database. This ultimately causes the crash since the keysdon'tmatch.

To find out if you are bound to a Network Account Server (NAS),navigate toSystem Preferences -> Users & Groups -> Login Options. See if there is anything listed underNetwork Account Server. If YES you are bound if NO you are not.

We believe as referenced in this article that this is a known issue with the Keystore on Mac Mojave O/S (10.14.4 and above). If you see the image below after resetting your password:

Knowledge Base Article

DO NOT OPEN AGINITY PRO until you take these actions to prevent you from losing your stored catalog and query history.

If you are reading this before you changed your password please take a backup now of your Catalog by following this documentation.

We also ask you take a copy of your current application log file which also does have a history of all executed SQL statements and their syntax just in case. You can do this by copying log.log from the ~/Library/Logs/aginity-prodirectory. This log will contain SQL that you can recover (see bottom of article)

Short Term Work Around

You can do these steps to access your catalog whether you open Aginity Pro or have not opened it after a domain-password reset we can walk you through these steps after updating to restore your existing encryption key into the Mac Keystore and Aginity Pro will work fine. If you are at all confused please contact us at [email protected] and we can do this interactively with you to ensure it goes smoothly!

1. Open up Finder in Mac and hit Command+Shift+G to open up the Goto Folder box

2. Enter "~/Library/Keychains to navigate to the users Keychain directory

3. In the Keychain directory you should see the old Keychain database file that was generated and archived when you hit the Update Keychain Password. The current one will be named login.keychain-db and you should see an archived one named login_renamed_1.keychain-db or the date and time should correspond to you hitting the Update Keychain Password button. Remember this file name for the next steps.

4. Launch the Keychain Access application by using the Apple Spotlight (CMD+Space) as shown:

5. Once you open it click the + button to add a new Keychain.

6. Add the archived keychain file (login_renamed_1.keychain-db or similar from Step 3)

7.After adding you should see it in the listing as shown below

8. Right click and select Unlock Keychain filename. You will need to enter in your old password (prior to the Domain change you just made) since this Keystore is the old one.

9. Search for the com.aginity.pro.database.key entry and Copy com.aginity.pro.database.key if you have not opened Aginity Pro orif you have opened Aginity Pro, Click on Copy Password to Clipboard.

10. If you have not Opened Aginity Pro, navigate to the top login keychain item and right click and select Paste com.aginity.pro.database.key as shown below since the entry does not exist, if you have opened Aginity Pro ignore this step and move onto Step 11.

11.If you have opened Aginity Pro there is a new entry for "com.aginity.pro.database.key" in the login Keychain but with the wrong encryption password. You will need to Right Click and choose Get Info, click the radio button for "Show Password", enter your current password twice and then Paste in the password from Step 9 as shown below. Don't forget to "Save Changes".

You know should be able to re-open Aginity Pro without error.

Ultimate Fix

Aginity will remove the need to rely on Apples keychain in our next release.

What If None of this Works then What?

If none of the above procedures work we prefer you submit a ticket at [email protected] and let us work with you to try to restore collaboratively with us but below are a few other options you may want to consider.

Re-installing Aginity Amp and Importing Catalog

If you have taken a recent export of the Catalog which can easily be re-imported into Aginity Pro after a completely fresh install it may be best to just do that. You will need to re-create your connections but it is probably an easier approach. To learn how to do a fresh install please reference this knowledge base article.

Recovering SQL from Current Application Log

After getting your log file saved as described above, please follow the Workaround section of this to do a clean install of Aginity Pro. Most important you must remove or rename the~/Library/Application Support/aginity-pro directory.

To recover SQL statements from your query history, the best thing we can do is mine our Log file to get at the SQL that was stored in Catalog. This is time consuming and we realize frustrating but all the SQLyou'vewritten is captured here

Start by Opening the Log File that you previously saved., log.log"

If you navigate to the top of the log and search for: "Execute query in provider: it will display each SQL statement executed and you will get those that you have run before and added to catalog as shown below.

2019-09-18 10:26:03.568 [server] INFO [dw-277 - POST /api/rpc/db-browser] c.a.a.p.d.BaseDataProvider - Execute query in provider: "select v1, ROW_NUMBER() OVER(ORDER BY ROWID) as ROWNUM from slug"2019-09-18 10:26:04.214 [server] INFO [dw-277 - POST /api/rpc/db-browser] c.a.a.p.d.BaseDataProvider - Reading is finished and 2 rows are read.

Aginity Netezza Workbench allows managing stored procedures easily and transparently.The stored procedures in a database are available under theStored Proceduresnode of the database in the object explorer tree.To create a stored procedure:1. Do one of the following:

a. Right-click theStored Proceduresnode of the database in the object explorer tree that you want to create the stored procedure for and selectCreate Procedurein the context menu.

b. In the object explorer tree, select the node of the database that you want to create the stored procedure for and then clickObject>Procedure>Create Procedurein the top menu.

2. In theGeneralsection of theStored Procedure Propertiesform, enter the name of the procedure and its language and specify whether you like to execute the procedure as the owner.Let's call the new procedure MY_NEW_PROCEDURE:

3. In theArgumentssection, enter the variables for the procedure and set their data types, precision, and scale.Let's specify one argument named "Result" here and select DATE as the data type for it:

Note that you can declare more variables later on if necessary, by editing the SQL query text.4. In theReturnssection of the form, select the data type, precision, and scale for the return data. You can also specify the reference table name here if necessary.In our example, we will select DATE as the data type:

ClickOKwhen done.5. As a result, a new tab is created in theQuery Editorwindow. The tab is named MY_NEW_PROCEDURE and contains the basic SQL query text that looks like the below:

Enter the query text at the cursor position between BEGIN and END.Let's enter the following here:

Result := MIN(DATE) FROM TABLE;

RETURN Result;

Now the code of the stored procedure looks like this:

When called, this procedure will return the minimum value from the DATE column of the TABLE1 table in the current database.6. Press CTL+F5 (execute as a single batch) to execute the SQL statement and finish creating the stored procedure. The name of the new stored procedure will appear in theStored Proceduresnode of the database in the object explorer tree.

In the latest release of Aginity Pro and Team, v.15.40 we have included the ability to copy the full JDBC connection string.

This is helpful for debugging what may be missing or required in the advanced parameter section when setting up database connections.

As always you should start with reading through our documentation on connecting to databases.

If you are still struggling the first thing we recommend is to look at the JDBC connection string as shown below.

When you selectCopy connection string to clipboardand then paste it to an editor you will see the following.

jdbc:redshift://snoopy-redshift.aginity.com:5439/snoopy_mart?allowMultiQueries=true;ssl=true;uid=jschlitt;pwd=*******;

This in coordination with your database administrator can now help you compare to the JDBC configuration guide of the database and determine what is missing. For example, maybe your Redshift configuration requires thesslRootCert parameter to point to a specific "*.pem" file. In this case you could add the advanced parameter as shown here and the corresponding JDBC configuration string.

jdbc:redshift://snoopy-redshift.aginity.com:5439/snoopy_mart?allowMultiQueries=true;ssl=true;sslRootCert=c:\sample\jeff.pem;uid=jschlitt;pwd=*****;

If you are unable to obtain a license duringthe Workbench install process or by email, please click this Submit a request link and provide the following information:

1. First Name2. Last name3. Company Name4. Country5. Platform required. Aginity Workbench is available for: a) IBM PureData for Analytics (Netezza) b) Amazon Redshift c) Pivotal Greenplum d) IBM dashDB e) Hadoop (Hive and Big SQL)

Aginity Pro provides the ability to supplement the base connection information with advanced properties. Using these advanced properties allow you to create a JDBC connection string compatible with your own environment. This may be useful if your organization secures database connections using SSL and or Knox gateways.

**NOTE: It is best to ask your DBAs or data platform administrator for the correct properties and values for your specific database connections.**

Hive

The connection string properties and values in the article here are accepted advanced properties for Hive. These properties and values are the same ones used to connect to your Hiveserver2 using beeline.

An example of Hive advanced properties can be seen below:

Knowledge Base article

IBM PureData System for Analytics (Netezza)

The connection string properties and values in the article here are accepted advanced properties for IBM PureData System for Analytics (Netezza).

An example of IBM PDSA advanced properties can be seen below:

Redshift

The connection string properties and values in the article here are accepted advanced properties for Amazon Redshift.

An example of Redshift advanced properties can be seen below:

Snowflake

The connection string properties and values in the article here are accepted advanced properties for Snowflake.

An example of Snowflake advanced properties can be seen below:

Note: Recently we released a feature that allows you to copy the JDBC connection string to help debug JDBC connectivity issues. Refer to this .

Attached is a document giving you a reference to the shortcut keys for Workbench.

Problem

Aginity Pro uses HTTPS to transmit user registration information to our licensing server and receives a license key through our Java application.

If the registration fails it may be due to antivirus software performing SSL scanning and acting as a proxy between our license server and the client software. When this happens our licensing server may reject the certificate if it is not properly signed.

The error message you may receive will look like this.

http://mcaf.ee/wgcbf

In our log files which can be found in the Help - Open Log File you will see an error similar to this.

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

This article will help you understand the nature of the issue and options you have to resolve it. Furthermore, we will be releasing a feature in the Aginity Pro that will notify you explicitly if the Java application is rejecting the certificate and will direct you to a web site to obtain a license via a browser versus relying on the Java application to generate it.

Cause

Whenever Java attempts to connect to another application over SSL (e.g.: HTTPS, IMAPS, LDAPS), it willonlybe able to connect to that application if it can trust it. The way trust is handled in the Java world is that you have a keystore (typically$JAVA_HOME/lib/security/cacerts), also known as the truststore.This contains a list of all known Certificate Authority (CA) certificates, and Java will only trust certificates that are signed by one of those CAs or public certificates that exist within thatkeystore.

Antivirus Software with SSL Scanning

If you are using antivirus software with SSL Scanning enabled, chances are Java is rejecting the certificate the antivirus software is supplying. This can typically be overcome by telling a browser to trust the antivirus software certificate but with Java programs it is a little harder since no browser is being used. To work with Java each downloading user would have to add a certificate to the Java keystore we ship our product with which is not an easy solution.

This article from McAfee does a really good job explaining how the SSL Scanning technology works in general.

Resolution

There are several resolutions to address this issue with varying degrees of complexity.

Resolving the Issue by Whitelisting Licensing Server URL

By whitelisting the URL for the Aginity Licensing server, you are telling the antivirus service to bypass it on SSL scanning. The server URL you will want to white list is: https://licensing.aginity.com

Resolving Issue by Making sure the Proxy Certificate from Antivirus Software is Trusted

Refer to your antivirus software manual on how to configure the SSL Scanning proxy with a trusted certificate versus the default which is usually untrusted. If it is trusted when the Java programs sees it, no error will be issued. The excerpt below is from McAfee's manual on installing the proxy certificate.

"You have two options to configure a Certificate Authority on the appliance:

First, you can generate a Certificate Authority directly within the user interface. Within the Web Gateway product guide, navigate toChapter 10 -> Web Filtering -> SSL Scanning -> Replace the default root certificate authority -> Create a root certificate Authority. Once this CA is generated, you can export that cert and push it out to your client workstations so they can trust it.

Second, you can import a local certificate authority onto the appliance. Many organizations use a local certificate authority (such as Microsofts CA) to sign their internal certs, and usually these are already trusted by domain workstations. Within the Web Gateway product guide, navigate toChapter 10 -> Web Filtering -> SSL Scanning -> Replace the default root certificate authority -> Import a root certificate Authority. For more information about generating the CA from your Microsoft CA, useKB75037()."

Generating Key Manually from Aginity Licensing Self Service Web Site

Going forward we will post our self-service licensing web site here. The main difference with using the web site is most likely your organization has already configured your browser to work with SSL Scanning and to trust the certificate sent from the Proxy.

Link coming soon!

hese release notes summarize the changes inAginity Workbench for PureData System for Analyticsversion4.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 )

Aginity Workbench version4.9contains a number of bug fixes.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested against Netezza Platform Software (NPS) versions7.2.1.3-P3, 7.2.0.3-P2, 7.1.0.4-P2, and 7.0.4.6-P3.

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 4.6.1

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.8

Bug Fixes in Build 4.9.1.2686

Severity

Reference

Description

Existed Since Version

Resolution

Moderate

15391

The User ID field is not visible on the connection dialog box after a user changes the 100% display setting to a larger setting.

2.5

The User ID field is visible on all display settings.

Minor

16045

The Discussion Forums menu item exists for the deprecated Aginity Forums.

2.4

The menu item was modified to go to the Aginity Community web forums.

Minor

16306

When importing an Excel file, the Data Import Wizard stops loading rows from the file on the first blank date field. Success is logged for the import job in this case.

2.5.1

Blank date fields are correctly processed, and an whole Excel file is properly imported.

Known Issues in Build 4.9.1.2686

Severity

Reference

Description

Workaround

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-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

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, select theDrop these entitiescheck box and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

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.

Run the script against the target schema.

Workaround 2:Generate two delta scripts

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, clear theDrop these entitiescheck box to not drop any tables, and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

Generate a delta script for the schemas again, selecting theDrop these entitiescheck box this time.

Save the script to another file.

First run the script file created in step 4 and then the one created in step 6.

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-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

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.

After connecting to Redshift, some users are reporting seeing the below error when trying to browse the catalog.

We are aware of this issue and are actively working on an update to Aginity Pro so this permission is not necessary. In the meantime, please see the workaround listed below.

Workaround: A DBA should grant select on table pg_user_info to the group your user is in

Final Release

Product

Version

ReleaseNotes

Link

Aginity Workbench for Redshift

4.9.3.2783

Release Notes

https://www.aginity.com/products/aginity-workbench/

Install & Configure the Amazon Redshift ODBC Driver

https://support.aginity.com/hc/en-us/articles/360015315014-How-to-Install-the-Native-Amazon-Redshift-ODBC-Driver

Previous Releases

Looking for an old version of Workbench :( ?

Instead, we encourage you to check out our latest products, Aginity Pro and Aginity Team !

Product

Version

ReleaseNotes

Aginity Workbench for Redshift

4.9.3.2778

Release Notes

Aginity Workbench for Redshift

4.9.1.2686

Release Notes

Aginity Workbench for Redshift

4.9.0.2677

Release Notes

Aginity Workbench for Redshift

4.8.0.2551

Release Notes

Aginity Workbench for Redshift

4.7.0.2454

Release Notes

Aginity Workbench for Redshift

4.6.0.2339

Release Notes

Aginity Workbench for Redshift

4.5.0.2319

Release Notes

Aginity Workbench for Redshift

4.4.2183.656

Release Notes

Aginity Workbench for Redshift

4.3.1962

Release Notes

If youmustobtain an old version of Workbench, please request one using the Submit a Request link at the top or bottom of this page.

These release notes summarize the changes in Aginity Workbench for Redshift 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 )

Aginity Workbench version 4.9 contains the following new features.

Support of the Amazon Redshift ODBC Driver

You can now make an ODBC connection to your Redshift database using the Amazon Redshift ODBC driver. The use of the Redshift ODBC driver allows you to choose from the following types of authentication for your connection:

Amazon Web Services (AWS) profile

AWSIdentity and Access Management (IAM) credentials

Single sign-on credentials (SSO) using one of the supported SAML 2.0 identity providers (if SSO is configured in your organization)

Standard authentication (a Redshift database user and password)

For instructions on how to download and install the Amazon Redshift ODBC driver, see the Amazon Redshift documentation. After you install the driver, depending on your version of Windows, select Amazon Redshift (x64) ODBC or Amazon Redshift (x32) ODBC in the driver list, in the lower-left corner of the database connection dialog box. To specify an authentication type for your connection, click Advanced, select the authentication type, and provide values for the required authentication properties.

Uploads to S3 Buckets with AWS KMS Encryption

When uploading data to your Amazon S3 bucket in the built-in S3 file explorer in Workbench, you can specify AWS KMS encryption for the data. Amazon S3 will encrypt each object with a unique key before it is saved to the bucket and decrypt it for you when you download it. For more information about AWS KMS encryption, see the documentation for the AWS Key Management Service.

You can also select AES-256 encryption or the default encryption (the one that is set for the bucket) for your uploads.

S3 Enhancements

The following changes were made to the Amazon S3 connection dialog box to enhance your S3 browsing experience:

Region Endpoint - Select the region to use in connecting to Amazon S3 and getting information about the regions of the buckets that you want to work with. We recommend that you select the region of one of the buckets in your AWS account. When connected to Amazon S3, you can open a bucket in the S3 file explorer.

Delimiter - You can specify a delimiter to override the default delimiter (/). The specified delimiter will be used in building a logical folder structure from the objects in your bucket and in creating or modifying objects in the S3 file explorer.

Technical Details and Changes

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

Upgrading from Prior Versions

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

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 4.6.1

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.8

Bug Fixes in Build 4.9.3.2783

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-1168

After upgrading to Aginity Workbench version 4.9 (build 4.9.3.2778), users encounter errors when they attempt to make a connection to a Redshift database.

4.9.3

Users can now successfully connect to a Redshift database.

Moderate

WPD-1174

The Show tables size feature works incorrectly. The Schema list displays multiple identical schemas. When a user selects a specific schema, no table metadata is shown.

4.8

The Show tables size feature works correctly.

Moderate

WPD-1175

The autocomplete feature works on table names, but doesnt work on columns.

4.8

The autocomplete feature now correctly displays a list of the columns from a selected table.

Moderate

WPD-1173

After upgrading to Aginity Workbench version 4.9 (build 4.9.3.2778), when a user runs a query that returns no rows (such as DROP, CREATE, or COMMIT), an empty result set tab is created.

4.9.3

A result set tab is correctly not created for such queries.

Bug Fixes in Build 4.9.3.2778

Aginity Workbench version 4.9.3 contains the following bug fixes.

Severity

Reference

Description

Existed Since Version

Resolution

Moderate

WPD-854

The S3 file explorer does not show the subfolders accessible to a user according to a bucket policy attached to the user in AWSIdentity and Access Management (IAM).

4.7

To have the Aginity Workbench S3 file explorer show the accessible folders in the bucket to a user according to the user's S3 bucket policy, you need to perform the following actions in both IAM and the S3 file explorer.

IAM

Make sure that:

The S3 bucket policy for the user contains the s3:ListBucket permission to allow listing the appropriate objects with a delimiter (for example a slash). You may also need to add the StringEquals condition with the ForAllValues prefix to the Condition block, as shown in this example:

{

"Sid": "AllowListingBucketFolder",

"Effect": "Allow",

"Action": "s3:ListBucket",

"Resource": "arn:aws:s3:::MyBucket",

"Condition": {

"ForAllValues:StringEquals": {

"s3:prefix": [

""

],

"s3:delimiter": "/"

}

}

}

The bucket policy explicitly denies listing without a delimiter. This is needed because of an S3 limitation.

Aginity Workbench S3 file explorer

When connecting to the bucket, clear the new Recursive directory access check box in the S3 dialog box. This will show all the top-level folders in the root of the bucket to the user, including the ones that are accessible to him or her according to the bucket policy.

In Aginity Workbench, selecting Recursive directory access specifies reading bucket objects without a delimiter.

If Recursive directory access is selected, a user that has access to only specific folders in the bucket according to his or her bucket policy will be denied access to the contents of the bucket in the S3 file explorer.

Minor

WPD-855

A query from a table that contains a decimal column with a precision greater than 28 digits (the maximum allowed by the Aginity Workbench UI) fails with an error.

4.7

The issue is resolved with the use of the Amazon Redshift ODBC driver. The driver provides a string representation of such long decimal values, and the string values are shown in the Query Analyzer window. Long decimals of more than 28 digits are still not supported in the rest of the UI because of the underlying .NET platform limitations.

Minor

WPD-824

When running a query from the pg_class system table in Redshift, a user gets an error "Unable to cast object of type 'System.Byte[]' to type 'System.IConvertible'. Couldn't store <System.Byte[]> in relexternid Column." The cause of the issue is that by default Redshift does not support displaying results of a query on a column of aclitem[]. acl data type.

4.8

The issue is resolved with the use of the Amazon Redshift ODBC driver. Queries from the pg_class system table are now run successfully.

Trivial

WPD-853

Although a user specifies in the result set options a number of rows to return by a query that is greater than 100,000, Workbench returns a maximum of 100,000 rows.

4.7

The maximum limit that a user can set on the number of rows to return by a query is 100,000. On-screen text was added next to the relevant result set option explicitly stating this limit.

Bug Fixes in Build 4.9.1.2686

Aginity Workbench version 4.9.1 contains the following bug fixes.

Severity

Reference

Description

Existed Since Version

Resolution

Moderate

APD-15391

The User ID field is not visible on the connection dialog box after a user changes the 100% display setting to a larger setting.

4.7

The User ID field is visible on all display settings.

Minor

APD-16045

The Discussion Forums menu item exists for the deprecated Aginity Forums.

4.7

The menu item was modified to go to the Aginity Community web forums.

Minor

APD-16442

The Data Import Wizard opens without displaying some of the file information fields (such as the name of the file being imported and the file compression type) and on-screen instructional text.

4.8

The Data Import Wizard now properly displays the file information fields and instructional text.

Known Issues in Build4.9.3.2783

Severity

Reference

Description

Workaround

Moderate

APD-4093

Import of a file from the S3 file explorer fails because invalid data types are set for the columns in the file.

Set data types for the columns manually.

Moderate

APD-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.

Moderate

WPD-680

Workbench generates invalid DDL when a user selects the Change Sort Keys command in the Object Browser.

N/A

Minor

APD-4090

If you begin a download using a file system explorer (such as Amazon S3) and abort the download, a small portion of the file remains on your target system.

Manually delete the file on your target system.

Minor

WPD-1182

The autocomplete feature does not display a list of columns from a table that has an alias in the FROM clause if the preceding query does end with a semicolon (;).

Add a semicolon at the end of the preceding query.

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.

Final Release

Product

Version

ReleaseNotes

Link

Aginity Workbench for PureData for Analytics

4.9.1.2686

Release Notes

https://www.aginity.com/products/aginity-workbench/

Previous Releases

Looking for an old version of Workbench :( ?

Instead, we encourage you to check out our latest products, Aginity Pro and Aginity Team !

Product

Version

ReleaseNotes

Aginity Workbench for PureData for Analytics

4.8.0.2551

Release Notes

Aginity Workbench for PureData for Analytics

4.7.0.2454

Release Notes

Aginity Workbench for PureData for Analytics

4.6.0.2339

Release Notes

Aginity Workbench for PureData for Analytics

4.5.0.2319

Release Notes

Aginity Workbench for PureData for Analytics

4.4.2193.678

Release Notes

Aginity Workbench for PureData for Analytics

4.3.1864

Release Notes

If you mustobtain an old version of Workbench, please request one using the Submit a Request link at the top or bottom of this page.

These release notes summarize the changes inAginity Workbench for PureData System for Analyticsversion4.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 version4.9:

The code autocompletion feature now displays functions in the list of matching database objects as a user starts typing a name in the Query Editor.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested against Netezza Platform Software (NPS) versions 7.2.0.3-P2 and NPS 7.1.0.4-P2 and NPS 7.0.4.6-P3.

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 4.61

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.7

New Features in Aginity Workbench 4.8.x

The following table details the features that were added in Aginity Workbench 4.8.x.

Reference

Version Added

Summary

WPD-277

Aginity Workbench 4.8

The code autocompletion feature now supports functions.

Bug Fixes in Build 4.8.1.2

Severity

Reference

Description

Existed Since Version

Resolution

Minor

APD-13878

An attempt to use the Re-check types option in the Data Import Wizard causes Aginity Workbench to crash. This occurs when the application is run on a Parallels Desktop for Mac virtual machine.

4.6

Fixed.

Bug Fixes in Build 4.8.0.2551

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-632

Workbench does not inform users when it is not possible to save changes to a query set.

4.4

Users are now properly informed why changes to a query set cannot be saved.

Major

WPD-736

Workbench makes excessive attempts to connect to a target server if invalid credentials are provided by a user.

4.6

Workbench now makes fewer attempts to connect to a target server in this situation.

Major

WPD-744

Using Ctrl + Page Down to create a tab in SQLEditor returns a gray read-only form.

4.7

The key combination Ctrl + Page Down is now used to switch between open tabs.

Moderate

WPD-359

Import from a JSON file fails because of a data type inconsistency.

4.3

The data type detection algorithm was modified.

Moderate

WPD-338

Changes that a user makes to individual queries in a query set are not saved.

4.4

Fixed.

Moderate

WPD-733, WPD-742

When a user attempts to create a stored procedure, an error "Input array is longer than the number of columns in this table" occurs.

4.7

Fixed.

Moderate

WPD-773

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.

4.7

Fixed.

Moderate

WPD-772

The order of objects in Object Explorer is incorrect if the list contains both case-sensitive and case-insensitive object names and Quoted Identifiers is unchecked.

4.7

Fixed.

Minor

WPD-766

The ESCAPE keyword is not highlighted.

4.3

Fixed.

Minor

WPD-5

An error occurs during import from a CSV file because the application incorrectly determines data types in the file.

4.4

Fixed.

Minor

WPD-737

The key combination Right Alt +4 does not work correctly on a Danish keyboard.

4.5

Fixed.

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.

4.6

Fixed.

Minor

WPD-739

The state of the query option "Enable Quick Info when the mouse hovers over a word in editor" is not preserved when a user exits Aginity Workbench.

4.7

Fixed.

Trivial

WPD-775

The Connect to Microsoft SQLServer screen has a background graphic that is misaligned with the text and controls on the screen. Functionality is not affected.

4.3

Fixed.

Known Issues in Build 4.8.1.2

Severity

Reference

Description

Workaround

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-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

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, select theDrop these entitiescheck box and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

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.

Run the script against the target schema.

Workaround 2:Generate two delta scripts

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, clear theDrop these entitiescheck box to not drop any tables, and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

Generate a delta script for the schemas again, selecting theDrop these entitiescheck box this time.

Save the script to another file.

First run the script file created in step 4 and then the one created in step 6.

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-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

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.

These release notes summarize the changes inAginity Workbench for PureData System for Analyticsversion4.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 version4.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.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested against Netezza Platform Software (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.6

Bug Fixes in Build4.7.0.2454

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.

Known Issues in Build4.7.0.2454

Severity

Reference

Description

Workaround

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

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, select theDrop these entitiescheck box and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

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.

Run the script against the target schema.

Workaround 2:Generate two delta scripts

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, clear theDrop these entitiescheck box to not drop any tables, and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

Generate a delta script for the schemas again, selecting theDrop these entitiescheck box this time.

Save the script to another file.

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 SQLServer 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.

These release notes summarize the changes inAginity Workbench for PureData System for Analyticsversion 4.6. 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.6:

Workbench can now detect Fluid Query data sources that are not registered in the System database.

The Show Distribution capability (visualizes data distribution over the SPUs in a user's system) is now supported on Netezza Striper 4 Rack systems.

Technical Details and Changes

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

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu 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.5

Bug Fixes in Build 4.6.0.2339

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-512

The Aginity CIA plugin is not compatible with Aginity Workbench version 4.5.

4.5

Fixed.

Major

WPD-530

Failure to detect Fluid Query sources not registered in the System database.

4.4

Fixed.

Moderate

WPD-91

The "Show Distribution" option shows incorrect results on a Striper 4 rack.

4.4

Fixed.

Known Issues in Build 4.6.0.2339

Severity

Reference

Description

Workaround

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

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, select theDrop these entitiescheck box and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

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.

Run the script against the target schema.

Workaround 2:Generate two delta scripts

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, clear theDrop these entitiescheck box to not drop any tables, and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

Generate a delta script for the schemas again, selecting theDrop these entitiescheck box this time.

Save the script to another file.

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 SQLServer 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.

Aginity Workbench for PureData System for Analyticsprovides 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.

The new search feature helps locate the database object you want in the Object Browser.A set of options is available to set search scope and narrow search results.

You can now bring code snippets from one Workbench into another by exporting them to a file and then importing them into a destination Workbench.

During import of large files, in addition to the first 1,000 rows in the file being analyzed by default, you have the option of analyzing more or all of the rows to have Workbench adjust their data types and column lengths.

During import, you have additional options for specifying what to do if the destination table exists.

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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu 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

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, select theDrop these entitiescheck box and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

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.

Run the script against the target schema.

Workaround 2:Generate two delta scripts

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, clear theDrop these entitiescheck box to not drop any tables, and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

Generate a delta script for the schemas again, selecting theDrop these entitiescheck box this time.

Save the script to another file.

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 SQLServer 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.

Aginity Workbench for PureData System for Analyticsprovides 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.4.

What's New?

Aginity Workbench now supports IBMFluid Query. Fluid Query helps you to directly query data on Hadoop clusters (using Hive, Big SQL, or Impala) and bring data from Hadoop to Netezza.

A built-in Workbench SQLFormatter is available in Workbench. In addition to using the built-in Workbench SQL Formatter, users can provide an alternative Windows Executable or .NET Assembly formatter. They can do so inApplication Options>SQL Formatters.

Technical Details and Changes

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

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested against NPS version 7.0.4 (P-1). No significant issues have been reported thus far with the use of Workbench on NPS versions 7.2.0.3-P2 and NPS 7.1.0.4-P2. Certification for these versions is coming up.

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.3

New Features

Reference

Summary

APD-6844

An option for ignoring SQL errors. SelectContinue on errorin the Query Options dialog box.

APD-8025

Support for the ReclaimNode, ReorgStatsNode, ReorgPrepNode, and ReorgMergeNode node types was added for parsing a Netezza Query Plan file. These node types are typically encountered in a GROOM TABLE plan.

WPD-93, WPD-41

You have a Fluid Query interface available in Workbench to access data on Hadoop server and transfer data from Hadoop.

WPD-1

A simple SQL format tool is available.

Bug Fixes in Build 4.4.2183

Severity

Reference

Description

Existed Since Version

Resolution

Major

APD-8795

After import from a JSON file that contains a dataset, only one record is added for the entire dataset.

4.3

Fixed. Data imported from a JSON file is now parsed into the correct number of records.

Major

APD-8086

A flat data structure is incorrectly parsed after import from a JSON file.

4.3

Fixed. Aflat structure is parsed into the correct number of records after import.

Major

APD-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.

4.3

Fixed.

Moderate

WPD-160

Abug occurs when a user creates an auxiliary Workbench stored procedure in a schema whose name uses case different from the default system case in Netezza.

4.2

Fixed.

Moderate

APD-6822

A DATE column from an Excel spreadsheet is imported into Workbench as an INTEGER column.

4.3

Fixed.

Moderate

APD-7787

When a user edits a stored procedure, the schema name is not included in the stored procedure name.

4.3

Fixed.

Moderate

APD-5202

When a user exports data using the Copy to Clipboard feature in the Export Data window, the SELECT AS statement shows up before the CREATE statement in the SQL code generated for the exported data.

4.3

Fixed. The CREATE statement is correctly shown before the SELECT AS statement.

Moderate

APD-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.

4.3

Fixed.

Moderate

APD-8630

When imported from an Excel sheet into Workbench, text fields show up as DECIMAL(3) columns.

4.3

Fixed. Text columns are correctly shown as VARCHAR after import.

Minor

WPD-88

Typo in the Restore Connections dialog box.

4.0

Fixed.

Minor

WPD-119

An issue with opening a user query history file created in a 32-bit version of Workbench in a 64-bit operating system.

4.2

Fixed.

Minor

APD-6925

Unable to generate a script with INSERT statements if a target table contains data in a column of INTERVAL type.

4.3

Fixed.

Minor

WPD-47

The SUM() function in Workbench returns a value with an incorrect decimal precision.

4.3

Fixed.

Minor

APD-8471

The entity list in the Object Browser is not refreshed after a user creates a new object (for example, a table) and then selects an appropriate refresh command on the Object menu (for example, "Refresh table list").

4.3

Fixed.

Known Issues in Build 4.4.2183

Severity

Reference

Description

Workaround

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

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, select theDrop these entitiescheck box and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

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.

Run the script against the target schema.

Workaround 2:Generate two delta scripts

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, clear theDrop these entitiescheck box to not drop any tables, and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

Generate a delta script for the schemas again, selecting theDrop these entitiescheck box this time.

Save the script to another file.

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 SQLServer 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.

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.

What's New?

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 SQLServer 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.

Technical Details and Changes

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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested against NPS 7.0.2-7.1.

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.2

New Features

Reference

Version Added

Summary

4870

4.2

Users can now work with versions 4.0 and 4.1 of theCustomer Insight for Retailplugin 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

Aforeign 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

Adelta 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" errorwhen connecting Aginity Workbench to Netezza 7.0.2.12.

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 SPUUtilization 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.

Minor

3780

Known Issues in Build 4.3.1864

Severity

Reference

Description

Workaround

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 databasewithout 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

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, select theDrop these entitiescheck box and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

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.

Run the script against the target schema.

Workaround 2:Generate two delta scripts

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, clear theDrop these entitiescheck box to not drop any tables, and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

Generate a delta script for the schemas again, selecting theDrop these entitiescheck box this time.

Save the script to another file.

First run the script file created in step 4 and then the one created in step 6.

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 SQLServer 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.

These release notes summarize the changes inAginity Workbench for Redshiftversion4.8. 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 version4.8:

The code autocompletion feature now displays functions in the list of matching database objects as a user starts typing a name in the Query Editor.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.8.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

Windows XP or later

Windows Installer 3.1

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.7

New Features in Aginity Workbench 4.8.x

The following table details the features that were added in Aginity Workbench 4.8.x.

Reference

Version Added

Summary

WPD-277

Aginity Workbench 4.8

The code autocompletion feature now supports functions.

Bug Fixes in Build 4.8.1.2

Severity

Reference

Description

Existed Since Version

Resolution

Minor

APD-13878

An attempt to use the Re-check types option in the Data Import Wizard causes Aginity Workbench to crash. This occurs when the application is run on a Parallels Desktop for Mac virtual machine.

4.6

Fixed.

Bug Fixes in Build 4.8.0.2551

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-632

Workbench does not inform users when it is not possible to save changes to a query set.

4.4

Users are now properly informed why changes to a query set cannot be saved.

Major

WPD-542

After a user generates DDL for a table with interleaved sort keys, Workbench incorrectly shows the number of sort keys in the Sort Keys node in the Object Browser or generates an error when the user attempts to expand the node.

4.4

Fixed.

Major

WPD-736

Workbench makes excessive attempts to connect to a target server if invalid credentials are provided by a user.

4.6

Workbench now makes fewer attempts to connect to a target server in this situation.

Major

WPD-744

Using Ctrl + Page Down to create a tab in SQLEditor returns a gray read-only form.

4.7

The key combination Ctrl + Page Down is now used to switch between open tabs.

Moderate

WPD-359

Import from a JSON file fails because of a data type inconsistency.

4.3

The data type detection algorithm was modified.

Moderate

WPD-693

A user gets an error when trying to create new code snippets or modify existing ones.

4.6

Fixed.

Moderate

WPD-733, WPD-742

When a user attempts to create a stored procedure, an error "Input array is longer than the number of columns in this table" occurs.

4.7

Fixed.

Moderate

WPD-773

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.

4.7

Fixed.

Moderate

WPD-772

The order of objects in Object Explorer is incorrect if the list contains both case-sensitive and case-insensitive object names and Quoted Identifiers is unchecked.

4.7

Fixed.

Minor

WPD-5

An error occurs during import from a CSV file because the application incorrectly determines data types in the file.

4.4

Fixed.

Minor

WPD-737

The key combination Right Alt +4 does not work correctly on a Danish keyboard.

4.5

Fixed.

Minor

WPD-743

Users cannot view the contents of an array of decimals.

4.7

Fixed. The contents of an array is now displayed in the Result tab.

Minor

WPD-739

The state of the query option "Enable Quick Info when the mouse hovers over a word in editor" is not preserved when a user exits Aginity Workbench.

4.7

Fixed.

Trivial

WPD-775

The Connect to Microsoft SQLServer screen has a background graphic that is misaligned with the text and controls on the screen. Functionality is not affected.

4.3

Fixed.

Known Issues in Build 4.8.1.2

Severity

Reference

Description

Workaround

Moderate

APD-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

APD-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.

Moderate

WPD-680

Workbench generates invalid DDL when a user selects the Change Sort Keys command in the Object Browser.

N/A

Minor

APD-4090

If you begin a download using a file system explorer (such as Amazon S3) and abort the download, a small portion of the file remains on your target system.

Manually delete the file on your target system.

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.

These release notes summarize the changes in Aginity Workbench for Redshift version 4.7. 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.7:

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.

Technical Details and Changes

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

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.

System Requirements

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

Full List of Changes Since Aginity Workbench 4.6

Bug Fixes in Build 4.7.0.2454

Severity

Reference

Description

Existed Since Version

Resolution

Moderate

WPD-179

Auser gets an error on attempt to generate an INSERT statement for a selected table in the Query Analyzer window.

4.6

Fixed.

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.

Known Issues in Build 4.7.0.2454

Severity

Reference

Description

Workaround

Major

WPD-542

After a user generates DDL for a table with interleaved sort keys, Workbench incorrectly shows the number of sort keys in the Sort Keys node in the Object Browser or generates an error when the user attempts to expand the node.

Manually update the generated DDL with the correct keys.

Moderate

APD-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

APD-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.

Moderate

WPD-693

A user gets an error when trying to create new code snippets or modify existing ones.

N/A.

Moderate

WPD-680

Workbench generates invalid DDL when a user selects the Change Sort Keys command in the Object Browser.

N/A

Minor

APD-4090

If you begin a download using a file system explorer (such as Amazon S3) and abort the download, a small portion of the file remains on your target system.

Manually delete the file on your target system.

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.

These release notes summarize the changes inAginity Workbench for Redshiftversion 4.6. The release notes also contain system requirements and list the known issues with the release.

Technical Details and Changes

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

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

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

Full List of Changes Since Aginity Workbench 4.5

Bug Fixes in Build 4.6.0.2339

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-564

Database object search fails with an error "ERROR: 42846: UNION/INTERSECT/EXCEPT could not convert type character varying to 'char'" on Redshift when a user searches entity names, entity bodies, or entity descriptions.

4.5

Fixed.

Known Issues in Build 4.6.0.2339

Severity

Reference

Description

Workaround

Major

WPD-542

After a user generates DDL for a table with interleaved sort keys, Workbench incorrectly shows the number of sort keys in the Sort Keys node in the Object Browser or generates an error when the user attempts to expand the node.

Manually update the generated DDL with the correct keys.

Moderate

APD-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

APD-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

APD-4090

If you begin a download using a file system explorer (such as Amazon S3) and abort the download, a small portion of the file remains on your target system.

Manually delete the file on your target system.

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.

Aginity Workbench for Redshiftprovides 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.

You can now bring code snippets from one Workbench into another by exporting them to a file and then importing them into a destination Workbench.

During import of large files, in addition to the first 1,000 rows in the file being analyzed by default, you have the option of analyzing more or all of the rows to have Workbench adjust their data types and column lengths.

During import, you have additional options for specifying what to do if the destination table exists.

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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

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

Full List of Changes Since Aginity Workbench 4.4

New Features

Reference

Summary

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.

Bug Fixes in Build 4.5.0.2319

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-327

Scripting the DDL for a table with a column of TIMESTAMP datatype produces invalid syntax.

4.4

Fixed.

Known Issues in Build 4.5.0.2319

Severity

Reference

Description

Workaround

Major

WPD-564

Database object search fails with an error "ERROR: 42846: UNION/INTERSECT/EXCEPT could not convert type character varying to 'char'" on Redshift when a user searches entity names, entity bodies, or entity descriptions.

N/A

Major

WPD-542

After a user generates DDL for a table with interleaved sort keys, Workbench incorrectly shows the number of sort keys in the Sort Keys node in the Object Browser or generates an error when the user attempts to expand the node.

Manually update the generated DDL with the correct keys.

Moderate

APD-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

APD-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

APD-4090

If you begin a download using a file system explorer (such as Amazon S3) and abort the download, a small portion of the file remains on your target system.

Manually delete the file on your target system.

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.

Aginity Workbench for Redshift 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.4.

What's New?

A built-in Workbench SQLFormatter is available in Workbench. In addition to using the built-in Workbench SQL Formatter, users can provide an alternative Windows Executable or .NET Assembly formatter. They can do so in Application Options > SQL Formatters.

Technical Details and Changes

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

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.

System Requirements

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

Full List of Changes Since Aginity Workbench 4.3

New Features

Reference

Summary

APD-6844

An option for ignoring SQL errors. Select Continue on error in the Query Options dialog box.

WPD-1

A simple SQL format tool is available.

APD-6910

Support for DISTSTYLE (ALL) was added to Workbench.

Bug Fixes in Build 4.4.2183

Severity

Reference

Description

Existed Since Version

Resolution

Major

APD-8795

After import from a JSON file that contains a dataset, only one record is added for the entire dataset.

4.3

Fixed. Data imported from a JSON file is now parsed into the correct number of records.

Major

APD-8086

A flat data structure is incorrectly parsed after import from a JSON file.

4.3

Fixed. Aflat structure is parsed into the correct number of records after import.

Major

WPD-170

An error appears when a user attempts to turn off "Group by Schema."

4.3

Fixed.

Major

WPD-68

In some cases when a user attempts to browse columns in a table, an error occurs indicating that an object reference is not set to an instance of an object.

4.3

Fixed.

Moderate

WPD-48, WPD-142

Querying large data sets on a Redshift server in SSL "Require" mode causes a "Connection is broken" error.

4.3

Fixed.

Minor

WPD-88

Typo in the Restore Connections dialog box.

4.0

Fixed.

Minor

APD-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.

4.3

Fixed.

Known Issues in Build 4.4.2183

Severity

Reference

Description

Workaround

Moderate

APD-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

APD-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

APD-4090

If you begin a download using a file system explorer (such as Amazon S3) and abort the download, a small portion of the file remains on your target system.

Manually delete the file on your target system.

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.

These release notes summarize the features and bug fixes that apply toAginity Workbench for Redshiftversion 4.3.

Highlights

Integration with Amazons 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 ofAginity Workbench for Redshift.

Download and install version 4.3 from the Aginity Workbench for Redshift Downloads page.

System Requirements

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

Features

Reference

Version Added

Summary

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

Severity

Reference

Description

Resolution

Moderate

7129

Leading zeros in VARCHAR values are lost after export to Excel.

Fixed.

Moderate

8090

When trying to execute an Explain SQLstatement 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.

Known Issues in Build 4.3.1962

Severity

Reference

Description

Workaround

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.

Final Release

Product

Version

ReleaseNotes

Link

Aginity Workbench for Hadoop

4.9.1.2686

Release Notes

https://www.aginity.com/products/aginity-workbench/

Previous Releases

Looking for an old version of Workbench :( ?

Instead, we encourage you to check out our latest products, Aginity Pro and Aginity Team !

Product

Version

ReleaseNotes

Aginity Workbench for Hadoop

4.8.0.2551

Release Notes

Aginity Workbench for Hadoop

4.7.0.2453

Release Notes

Aginity Workbench for Hadoop

4.6.0.2339

Release Notes

Aginity Workbench for Hadoop

4.5.0.2319

Release Notes

If youmustobtain an old version of Workbench, please request one using the Submit a Request link at the top or bottom of this page.

These release notes summarize the changes inAginity Workbench for Hadoopversion4.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 )

Aginity Workbench version4.9contains a number of bug fixes.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested on Hive 1.1 (CDH 5.4), Hive 0.14, Hive 0.12, and Big SQL (BigInsights 3 and 4).

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 4.6.1

The IBM Data Server Driver Package is installed on your client computer (for Big SQL connections).

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.8

Bug Fixes in Build 4.9.1.2686

Severity

Reference

Description

Existed Since Version

Resolution

Major

16307

When a user attempts to import a file into a Hive table using the Data Import Wizard, the wizard displays the first HDFS connection created in Query Analyzer, and that connection cannot be changed. If the preselected HDFS connection and the Hive connection selected by the user point to different clusters, the import results in an empty target table although the Job Monitor reports success.

2.5.1

Adialog box allowing the user to select an HDFS connection for import was added as the first step of the wizard. If a selected HDFS connection and the Hive connection are located on different clusters, the Job Monitor reports failure and provides a corresponding warning.

Moderate

15391

The User ID field is not visible on the connection dialog box after a user changes the 100% display setting to a larger setting.

2.5

The User ID field is visible on all display settings.

Moderate

16277

When a user executes an SQL statement to load data from a file into a table using the LOAD DATA INPATH command, a "Null Pointer Exception"error generated by Hive appears in the Output window. However, the data is successfully loaded into the table.

2.5.3

The error message is now suppressed.

Minor

16045

The Discussion Forums menu item exists for the deprecated Aginity Forums.

2.4

The menu item was modified to go to the Aginity Community web forums.

Minor

15089

Importing a file into a nonexisting table on Hive where metastore connection information is not provided fails.

2.5

Fixed.

Minor

16311

When a user runs a query to export a table to Hive in Query Analyzer, a Java error message appears in the Output window although the export is completed successfully.

2.5.1

The error message is suppressed in this situation.

Known Issues in Build 4.9.1.2686

Severity

Reference

Description

Workaround

Moderate

WPD-348

When connected to the Hadoop cluster through Big SQL, a user attempts to insert data into an existing table, but the INSERT statement returns a message saying "0 rows affected" although the rows are in fact inserted.

N/A

Moderate

WPD-819

Generate Insert DML command (available from the Advanced menu) does not function for Hive tables. You will receive an error indicating the there was an error when compiling the statement.

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.

These release notes summarize the changes inAginity Workbench for Hadoopversion4.8. 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 version4.8:

Kerberos-authenticated connections are now supported.

The code autocompletion feature now displays functions in the list of matching database objects as a user starts typing a name in the Query Editor.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.8.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested on Hive 1.1 (CDH 5.4), Hive 0.14, Hive 0.12, and Big SQL (BigInsights 3 and 4).

System Requirements

Windows XP or later

Windows Installer 3.1

The IBM Data Server Driver Package is installed on your client computer (for Big SQL connections).

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.7

New Features in Aginity Workbench 4.8.x

The following table details the features that were added in Aginity Workbench 4.8.x.

Reference

Version Added

Summary

WPD-277

Aginity Workbench 4.8

The code autocompletion feature now supports functions.

WPD-562

Aginity Workbench 4.8

Hadoop systems secured by Kerberos are supported.

Bug Fixes in Build 4.8.1.2

Severity

Reference

Description

Existed Since Version

Resolution

Major

APD-14333

With the query timeout set to longer than 120 seconds, Aginity Workbench times out on queries longer than 120 seconds in HTTP mode.

4.6

Fixed. Queries now run to completion on any timeout setting.

Minor

APD-13878

An attempt to use the Re-check types option in the Data Import Wizard causes Aginity Workbench to crash. This occurs when the application is run on a Parallels Desktop for Mac virtual machine.

4.6

Fixed.

Minor

APD-13462

Code snippets don't work in Aginity Workbench for PostgreSQL.

4.6

Code snippets now work properly.

Minor

APD-14284

The connection timeout value that a user enters in the connection dialog box is not saved when the user reopens the application.

4.6

The connection timeout value entered by a user is properly preserved.

Bug Fixes in Build 4.8.0.2551

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-632

Workbench does not inform users when it is not possible to save changes to a query set.

4.4

Users are now properly informed why changes to a query set cannot be saved.

Major

WPD-618

Import into Workbench for Hive fails if a user chooses the BIGDECIMAL or NUMERIC data type for the import. These data types are present in Workbench but are not supported by Hive.

4.5

The BIGDECIMAL and NUMERIC data types were removed.

Major

WPD-736

Workbench makes excessive attempts to connect to a target server if invalid credentials are provided by a user.

4.6

Workbench now makes fewer attempts to connect to a target server in this situation.

Major

WPD-744

Using Ctrl + Page Down to create a tab in SQLEditor returns a gray read-only form.

4.7

The key combination Ctrl + Page Down is now used to switch between open tabs.

Moderate

WPD-359

Import from a JSON file fails because of a data type inconsistency.

4.3

The data type detection algorithm was modified.

Moderate

WPD-733, WPD-742

When a user attempts to create a stored procedure, an error "Input array is longer than the number of columns in this table" occurs.

4.7

Fixed.

Moderate

WPD-773

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.

4.7

Fixed.

Moderate

WPD-772

The order of objects in Object Explorer is incorrect if the list contains both case-sensitive and case-insensitive object names and Quoted Identifiers is unchecked.

4.7

Fixed.

Moderate

WPD-703

A user with the required permissions is unable to display a list of user sessions.

4.7

Fixed.

Minor

WPD-5

An error occurs during import from a CSV file because the application incorrectly determines data types in the file.

4.4

Fixed.

Minor

WPD-737

The key combination Right Alt +4 does not work correctly on a Danish keyboard.

4.5

Fixed.

Minor

WPD-739

The state of the query option "Enable Quick Info when the mouse hovers over a word in editor" is not preserved when a user exits Aginity Workbench.

4.7

Fixed.

Trivial

WPD-775

The Connect to Microsoft SQLServer screen has a background graphic that is misaligned with the text and controls on the screen. Functionality is not affected.

4.3

Fixed.

Known Issues in Build 4.8.1.2

Severity

Reference

Description

Workaround

Moderate

WPD-348

When connected to the Hadoop cluster through Big SQL, a user attempts to insert data into an existing table, but the INSERT statement returns a message saying "0 rows affected" although the rows are in fact inserted.

N/A

Moderate

WPD-819

Generate Insert DML command (available from the Advanced menu) does not function for Hive tables. You will receive an error indicating the there was an error when compiling the statement.

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.

These release notes summarize the changes inAginity Workbench for Hadoopversion4.7. 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 version4.7:

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.

(If connected to Big SQL) You can achieve faster performance populating the Object Browser with database objects by setting the application to not automatically read certain Hive information for tables in the application options.

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.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.7.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested on Hive 1.1 (CDH 5.4), Hive 0.14, Hive 0.12, and Big SQL (BigInsights 3 and 4).

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 3.5 SP1

The IBM Data Server Driver Package is installed on your client computer (for Big SQL connections).

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.6

Bug Fixes in Build4.7.0.2453

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-357

A line "ODBC Version: Unknown or not installed" is displayed in the System Information dialog box when an ODBC driver is not used.

4.6

Fixed. The ODBC Version line is now hidden when an ODBC driver is not used.

Moderate

WPD-637

Importing a file into Big SQL causes an error because the length of string columns in the file is calculated in characters.

4.5

Fixed. The length of string columns is now calculated in bytes.

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-550

In the event of failure to import a CSV file, a user attempts to reopen the file in the Import Wizard from the Job Monitor, but gets an error.

4.5

Fixed. On failure to import a file,a user can now reopen the file to the initial parameters in the Import Wizard by using the failed job in the Job Monitor.

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.

Known Issues in Build4.7.0.2453

Severity

Reference

Description

Workaround

Major

WPD-618

Import into Workbench for Hive fails if a user chooses the BIGDECIMAL or NUMERIC data type for the import. These data types are present in Workbench but are not supported by Hive.

The BIGDECIMAL and NUMERIC data types will be removed in a future version of Workbench. For now, replace them with other appropriate data types for your import.

Moderate

WPD-348

When connected to the Hadoop cluster through Big SQL, a user attempts to insert data into an existing table, but the INSERT statement returns a message saying "0 rows affected" although the rows are in fact inserted.

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.

These release notes summarize the changes inAginity Workbench for Hadoopversion 4.6. The release notes also contain system requirements and list the known issues with the release.

Hardware and Software Support

Aginity Workbench for Hadoophas been tested on Hive 1.1 (CDH 5.4), Hive 0.14 (HDP 2.2), Hive 0.12, and Big SQL (BigInsights 3).

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 3.5 SP1

The IBM Data Server Driver Package is installed on your client computer (for Big SQL connections).

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.5

Bug Fixes in Build 4.6.0.2339

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-574

All Hive queries time out after 120 seconds. This is caused by the Query timeout option in Workbench not being honored.

4.5

Fixed. Workbench was modified to honor the Query timeout.

Major

WPD-563

Import into Workbench for Hive fails if a user chooses the INTEGER data type for the import. This issue is caused by Workbench supporting INTEGER, not the Hive-supported INT.

4.5

Fixed. INTEGER was replaced with INT.

Moderate

WPD-548

When connected to the Hadoop cluster through Hive, a user tries to open Job Tracker Configuration and Task Tracker Configuration from the Server node in the Object Browser but gets an error.

4.5

Fixed.

Known Issues in Build 4.6.0.2339

Severity

Reference

Description

Workaround

Major

WPD-618

Import into Workbench for Hive fails if a user chooses the BIGDECIMAL or NUMERIC data type for the import. These data types are present in Workbench but are not supported by Hive.

The BIGDECIMAL and NUMERIC data types will be removed in a future version of Workbench. For now, replace them with other appropriate data types for your import.

Moderate

WPD-348

When connected to the Hadoop cluster through Big SQL, a user attempts to insert data into an existing table, but the INSERT statement returns a message saying "0 rows affected" although the rows are in fact inserted.

N/A

Minor

WPD-550

When connected to the Hadoop cluster through Big SQL, a user attempts to import a .csv file into an existing table and then chooses the Existing Table Action" of "Do Not Import." When the import correctly fails, the user clicks "Show More Details"in Job Monitor to get more detail on the failed rows but instead gets an error message.

N/A

These release notes provide installation instructions forAginity Workbench for Hadoopversion 4.5, contain system requirements, and list the known issues with the release.

Installing Workbench

DownloadAginity Workbench for Hadoop.

Save the Workbench executable file to a location on your computer.

Run the executable file to display the installation wizard.

Follow the instructions on the wizard pages to complete the installation.

Hardware and Software Support

Aginity Workbench for Hadoophas been tested on Hive 1.1 (CDH 5.4), Hive 0.14 (HDP 2.2), Hive 0.12, and Big SQL (BigInsights 3).

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 3.5 SP1

The IBM Data Server Driver Package is installed on your client computer (for Big SQL connections).

Memory: 256 MB RAM

Disk space: 100 MB, plus any necessary space for .NET Framework and Windows Installer

Known Issues in Build 4.5.0.2319

Severity

Reference

Description

Workaround

Moderate

WPD-348

When connected to the Hadoop cluster through Big SQL, a user attempts to insert data into an existing table, but the INSERT statement returns a message saying "0 rows affected" although the rows are in fact inserted.

N/A

Moderate

WPD-548

When connected to the Hadoop cluster through Hive, a users tries to open Job Tracker Configuration and Task Tracker Configuration from the Server node in the Object Browser but gets an error.

N/A

Minor

WPD-550

When connected to the Hadoop cluster through Big SQL, a user attempts to import a .csv file into an existing table and then chooses the Existing Table Action" of "Do Not Import." When the import correctly fails, the user clicks "Show More Details"in Job Monitor to get more detail on the failed rows but instead gets an error message.

N/A

Minor

WPD-487

When connected to the Hadoop cluster through Hive, a user attempts to reverse-engineer a database and selects the Data Dictionaries box in the Script Database window. The reverse-engineering operation fails with an error "the method or operation is not implemented."

Hive does not have a traditional SQL information schema. Use the SHOW command as specified here: https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Show.

Final Release

Product

Version

ReleaseNotes

Link

Aginity Workbench for dashDB

4.9.1.2686

Release Notes

x86: https://www.aginity.com/WB/dashDB/x86/files/AginityDashDBWorkbenchSetupx86.exe x64: https://www.aginity.com/WB/dashDB/x64/files/AginityDashDBWorkbenchSetupx64.exe

Previous Releases

Looking for an old version of Workbench :( ?

Product

Version

ReleaseNotes

Aginity Workbench for dashDB

4.8.0.2551

Release Notes

Aginity Workbench for dashDB

4.7.0.2454

Release Notes

Aginity Workbench for dashDB

4.5.0.2319

Release Notes

Aginity Workbench for dashDB

4.4.2183.656

Release Notes

Aginity Workbench for dashDB

4.3.2059

Release Notes

If youmustobtain an old version of Workbench, please request one using the Submit a Request link at the top or bottom of this page.

These release notes summarize the changes inAginity Workbench for dashDBversion4.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 )

Aginity Workbench version4.9contains a number of bug fixes.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 4.6.1

A client package containing required dashDB drivers. The package can be downloaded and installed from the dashDB Web Console.

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.8

Bug Fixes in Build 4.9.1.2686

Severity

Reference

Description

Existed Since Version

Resolution

Moderate

15391

The User ID field is not visible on the connection dialog box after a user changes the 100% display setting to a larger setting.

2.5

The User ID field is visible on all display settings.

Minor

16045

The Discussion Forums menu item exists for the deprecated Aginity Forums.

2.4

The menu item was modified to go to the Aginity Community web forums.

Known Issues in Build 4.9.1.2686

Severity

Reference

Description

Workaround

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.

These release notes summarize the changes inAginity Workbench for dashDBversion4.8. 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 version4.8:

The code autocompletion feature now displays functions in the list of matching database objects as a user starts typing a name in the Query Editor.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.8.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

Windows XP or later

Windows Installer 3.1

A client package containing required dashDB drivers. The package can be downloaded and installed from the dashDB Web Console.

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.7

New Features in Aginity Workbench 4.8.x

The following table details the features that were added in Aginity Workbench 4.8.x.

Reference

Version Added

Summary

WPD-277

Aginity Workbench 4.8

The code autocompletion feature now supports functions.

Bug Fixes in Build 4.8.1.2

Severity

Reference

Description

Existed Since Version

Resolution

Minor

APD-13878

An attempt to use the Re-check types option in the Data Import Wizard causes Aginity Workbench to crash. This occurs when the application is run on a Parallels Desktop for Mac virtual machine.

4.6

Fixed.

Bug Fixes in Build 4.8.0.2551

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-632

Workbench does not inform users when it is not possible to save changes to a query set.

4.4

Users are now properly informed why changes to a query set cannot be saved.

Major

WPD-736

Workbench makes excessive attempts to connect to a target server if invalid credentials are provided by a user.

4.6

Workbench now makes fewer attempts to connect to a target server in this situation.

Major

WPD-744

Using Ctrl + Page Down to create a tab in SQLEditor returns a gray read-only form.

4.7

The key combination Ctrl + Page Down is now used to switch between open tabs.

Moderate

WPD-359

Import from a JSON file fails because of a data type inconsistency.

4.3

The data type detection algorithm was modified.

Moderate

WPD-733, WPD-742

When a user attempts to create a stored procedure, an error "Input array is longer than the number of columns in this table" occurs.

4.7

Fixed.

Moderate

WPD-773

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.

4.7

Fixed.

Moderate

WPD-772

The order of objects in Object Explorer is incorrect if the list contains both case-sensitive and case-insensitive object names and Quoted Identifiers is unchecked.

4.7

Fixed.

Minor

WPD-5

An error occurs during import from a CSV file because the application incorrectly determines data types in the file.

4.4

Fixed.

Minor

WPD-737

The key combination Right Alt +4 does not work correctly on a Danish keyboard.

4.5

Fixed.

Minor

WPD-739

The state of the query option "Enable Quick Info when the mouse hovers over a word in editor" is not preserved when a user exits Aginity Workbench.

4.7

Fixed.

Trivial

WPD-775

The Connect to Microsoft SQLServer screen has a background graphic that is misaligned with the text and controls on the screen. Functionality is not affected.

4.3

Fixed.

Known Issues in Build 4.8.1.2

Severity

Reference

Description

Workaround

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.

These release notes summarize the changes inAginity Workbench for dashDBversion4.7. 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 version4.7:

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.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.7.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 3.5 SP1

A client package containing required dashDB drivers. The package can be downloaded and installed from the dashDB Web Console.

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.6

Bug Fixes in Build4.7.0.2454

Severity

Reference

Description

Existed Since Version

Resolution

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.

Known Issues in Build4.7.0.2454

Severity

Reference

Description

Workaround

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.

Aginity Workbench for dashDBprovides 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.

The new search feature helps locate the database object you want in the Object Browser.A set of options is available to set search scope and narrow search results.

You can now bring code snippets from one Workbench into another by exporting them to a file and then importing them into a destination Workbench.

During import of large files, in addition to the first 1,000 rows in the file being analyzed by default, you have the option of analyzing more or all of the rows to have Workbench adjust their data types and column lengths.

During import, you have additional options for specifying what to do if the destination table exists.

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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 3.5 SP1

A client package containing required dashDB drivers. The package can be downloaded and installed from the dashDB Web Console.

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.

Known Issues in Build 4.5.0.2319

Severity

Reference

Description

Workaround

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.

Aginity Workbench for dashDBprovides 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.4.

What's New?

A built-in Workbench SQLFormatter is available in Workbench. In addition to using the built-in Workbench SQL Formatter, users can provide an alternative Windows Executable or .NET Assembly formatter. They can do so inApplication Options>SQL Formatters.

Technical Details and Changes

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

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 3.5 SP1

A client package containing required dashDB drivers. The package can be downloaded and installed from the dashDB Web Console.

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.3

New Features

Reference

Summary

APD-6844

An option for ignoring SQL errors. SelectContinue on errorin the Query Options dialog box.

WPD-1

A simple SQL format tool is available.

Bug Fixes in Build 4.4.2183

Severity

Reference

Description

Existed Since Version

Resolution

Major

APD-8795

After import from a JSON file that contains a dataset, only one record is added for the entire dataset.

4.3

Fixed. Data imported from a JSON file is now parsed into the correct number of records.

Major

APD-8086

A flat data structure is incorrectly parsed after import from a JSON file.

4.3

Fixed. Aflat structure is parsed into the correct number of records after import.

Minor

WPD-88

Typo in the Restore Connections dialog box.

4.0

Fixed.

Known Issues in Build 4.4.2183

Severity

Reference

Description

Workaround

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.

Aginity Workbench for dashDBis a free client-side application that allows users to connect to their dashDB instance and query data there.

These release notes summarize the main features ofAginity Workbench for dashDBversion 4.3 and provide instructions on installation of this version.

Features

This section lists the main features of Aginity Workbench in descending order by release.

Build 4.3.2059

Migrate your Netezza data models and data to dashDB.

View various aspects of space allocation information for the tables in your database.

Run all statements within a script in a transaction. You can specify whether transactions are committed explicitly (manually) or implicitly (after each successfully completed statement).

Build 4.3.2002

Establish a Secure Sockets Layer (SSL) connection to your dashDB instance.

Execute one or multiple SQL queries.

Edit queries in the SQL Editor.

Generate complete and accurate DDL for all schema objects (tables, views, materialized query tables, sequences, and so on), including the option of generating DDL for an entire schema.

Create and call stored procedures in Workbench.

Create SQL templates with parameterized values for easier storage and reuse.

Explore all the schemas in your dashDB database and view the objects in each schema in an Object Explorer.

Drag and drop schema objects from the Object Explorer into the Query Editor to insert the text where the pointer is currently positioned.

Save a current query to a file or save all currently open queries as a single query set file to edit or execute the queries later.

Create code snippets for reuse in queries.

Create and insert bookmarks within a long query to help you jump to appropriate SQL statements.

Create and apply filters to objects in the Object Explorer.

Generate an explanation of how a query is going to be executed.

Import data from an external database or from a file in one of the supported formats.

Execute an SQL statement as a single batch (not as a series of SQL statements).

Visualize various aspects of a result set.

Have SQLcode auto-completed as you type it.

Create, test, and deploy SQL-based user-defined scalar and table functions.

Run load tests on your database.

Log data related to SQL query execution.

Execute SQL statements in command-line mode using the Workbench Command Line Builder.

Installation Instructions

Download and install version 4.3 from the Aginity Workbench for dashDB Downloads page.

System Requirements

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.

Final Release

Product

Version

ReleaseNotes

Link

Aginity Workbench for Greenplum

4.9.1.2686

Release Notes

x86: https://www.aginity.com/WB/GP/x86/files/AginityGreenplumWorkbenchSetupx86.exe x64: https://www.aginity.com/WB/GP/x64/files/AginityGreenplumWorkbenchSetupx64.exe ch/

Previous Releases

Looking for an old version of Workbench :( ?

Instead, we encourage you to check out our latest products, Aginity Pro and Aginity Team !

Product

Version

ReleaseNotes

Aginity Workbench for Greenplum

4.8.0.2551

Release Notes

Aginity Workbench for Greenplum

4.7.0.2454

Release Notes

Aginity Workbench for Greenplum

4.5.0.2319

Release Notes

Aginity Workbench for Greenplum

4.4.2192.674

Release Notes

Aginity Workbench for Greenplum

4.3.2032

Release Notes

If youmustobtain an old version of Workbench, please request one using the Submit a Request link at the top or bottom of this page.

These release notes summarize the changes inAginity Workbench for Greenplumversion4.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 )

Aginity Workbench version4.9contains a number of bug fixes.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

Windows XP or later

Windows Installer 3.1

.NET Framework 4.6.1

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.8

Bug Fixes in Build 4.9.1.2686

Severity

Reference

Description

Existed Since Version

Resolution

Moderate

15391

The User ID field is not visible on the connection dialog box after a user changes the 100% display setting to a larger setting.

2.5

The User ID field is visible on all display settings.

Minor

16045

The Discussion Forums menu item exists for the deprecated Aginity Forums.

2.4

The menu item was modified to go to the Aginity Community web forums.

Known Issues in Build 4.9.1.2686

Severity

Reference

Description

Workaround

Moderate

APD-5977

The SECURITY DEFINER setting is ignored during export of a function.

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.

These release notes summarize the changes inAginity Workbench for Greenplumversion4.8. 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 version4.8:

The code autocompletion feature now displays functions in the list of matching database objects as a user starts typing a name in the Query Editor.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.8.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

Windows XP or later

Windows Installer 3.1

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.7

New Features in Aginity Workbench 4.8.x

The following table details the features that were added in Aginity Workbench 4.8.x.

Reference

Version Added

Summary

WPD-277

Aginity Workbench 4.8

The code autocompletion feature now supports functions.

Bug Fixes in Build 4.8.1.2

Severity

Reference

Description

Existed Since Version

Resolution

Minor

APD-13878

An attempt to use the Re-check types option in the Data Import Wizard causes Aginity Workbench to crash. This occurs when the application is run on a Parallels Desktop for Mac virtual machine.

4.6

Fixed.

Bug Fixes in Build 4.8.0.2551

Severity

Reference

Description

Existed Since Version

Resolution

Major

WPD-632

Workbench does not inform users when it is not possible to save changes to a query set.

4.4

Users are now properly informed why changes to a query set cannot be saved.

Major

WPD-736

Workbench makes excessive attempts to connect to a target server if invalid credentials are provided by a user.

4.6

Workbench now makes fewer attempts to connect to a target server in this situation.

Major

WPD-744

Using Ctrl + Page Down to create a tab in SQLEditor returns a gray read-only form.

4.7

The key combination Ctrl + Page Down is now used to switch between open tabs.

Major

WPD-763

Import from a CSV file is not working.

4.7

Fixed.

Moderate

WPD-359

Import from a JSON file fails because of a data type inconsistency.

4.3

The data type detection algorithm was modified.

Moderate

WPD-733, WPD-742

When a user attempts to create a stored procedure, an error "Input array is longer than the number of columns in this table" occurs.

4.7

Fixed.

Moderate

WPD-773

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.

4.7

Fixed.

Moderate

WPD-772

The order of objects in Object Explorer is incorrect if the list contains both case-sensitive and case-insensitive object names and Quoted Identifiers is unchecked.

4.7

Fixed.

Minor

WPD-5

An error occurs during import from a CSV file because the application incorrectly determines data types in the file.

4.4

Fixed.

Minor

WPD-737

The key combination Right Alt +4 does not work correctly on a Danish keyboard.

4.5

Fixed.

Minor

WPD-753

Import of a file fails because of a syntax error.

4.7

Fixed.

Minor

WPD-743

Users cannot view the contents of an array of decimals.

4.7

Fixed. The contents of an array is now displayed in the Result tab.

Minor

WPD-739

The state of the query option "Enable Quick Info when the mouse hovers over a word in editor" is not preserved when a user exits Aginity Workbench.

4.7

Fixed.

Trivial

WPD-775

The Connect to Microsoft SQLServer screen has a background graphic that is misaligned with the text and controls on the screen. Functionality is not affected.

4.3

Fixed.

Known Issues in Build 4.8.1.2

Severity

Reference

Description

Workaround

Moderate

APD-5977

The SECURITY DEFINER setting is ignored during export of a function.

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.

These release notes summarize the changes inAginity Workbench for Greenplumversion4.7. 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 version4.7:

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.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench4.7.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

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

Full List of Changes Since Aginity Workbench 4.6

Bug Fixes in Build4.7.0.2454

Severity

Reference

Description

Existed Since Version

Resolution

Moderate

WPD-654

Clicking the Database Maintenance button generates incorrect SQL code.

4.5

Fixed.

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.

Known Issues in Build4.7.0.2454

Severity

Reference

Description

Workaround

Moderate

APD-5977

The SECURITY DEFINER setting is ignored during export of a function.

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.

Aginity Workbench for Greenplumprovides 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.

The new search feature helps locate the database object you want in the Object Browser.A set of options is available to set search scope and narrow search results.

You can now bring code snippets from one Workbench into another by exporting them to a file and then importing them into a destination Workbench.

During import of large files, in addition to the first 1,000 rows in the file being analyzed by default, you have the option of analyzing more or all of the rows to have Workbench adjust their data types and column lengths.

During import, you have additional options for specifying what to do if the destination table exists.

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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

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

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.

Known Issues in Build 4.5.0.2319

Severity

Reference

Description

Workaround

Moderate

APD-5977

The SECURITY DEFINER setting is ignored during export of a function.

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.

Aginity Workbench for Greenplumprovides 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.4.

What's New?

A built-in Workbench SQLFormatter is available in Workbench. In addition to using the built-in Workbench SQL Formatter, users can provide an alternative Windows Executable or .NET Assembly formatter. They can do so inApplication Options>SQL Formatters.

Technical Details and Changes

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

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

System Requirements

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

Full List of Changes Since Aginity Workbench 4.3

New Features

Reference

Summary

APD-6844

An option for ignoring SQL errors. SelectContinue on errorin the Query Options dialog box.

WPD-1

A simple SQL format tool is available.

Bug Fixes in Build 4.4.2183

Severity

Reference

Description

Existed Since Version

Resolution

Critical

WPD-159

When a user exports an empty table to a file, an error occurs.

3.x

Fixed.

Critical

WPD-251

Under certain circumstances, when a user expands the Tables, External Tables, or Views node for a schema in the Object Browser, no tables or views are listed below.

4.4

Fixed.

Major

APD-6459

When a user edits a function that has comments, in some cases saving it may cause the comments to be deleted.

4.0

Fixed.

Major

APD-6444

A type mismatch error occurs when a user selects a column with a type of BIT.

4.0

Fixed.

Major

APD-8795

After import from a JSON file that contains a dataset, only one record is added for the entire dataset.

4.3

Fixed. Data imported from a JSON file is now parsed into the correct number of records.

Major

APD-8086

A flat data structure is incorrectly parsed after import from a JSON file.

4.3

Fixed. Aflat structure is parsed into the correct number of records after import.

Major

WPD-68

In some cases when a user attempts to browse columns in a table, an error occurs indicating that an object reference is not set to an instance of an object.

4.3

Fixed.

Minor

WPD-88

Typo in the Restore Connections dialog box.

4.0

Fixed.

Known Issues in Build 4.4.2183

Severity

Reference

Description

Workaround

Moderate

APD-5977

The SECURITY DEFINER setting is ignored during export of a function.

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.

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.

What's New?

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 SQLServer 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.

Technical Details and Changes

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, selectInstall this update nowto 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 clickingCheck for Updateson theHelpmenu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested against NPS 7.0.2-7.1.

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.2

New Features

Reference

Version Added

Summary

4870

4.2

Users can now work with versions 4.0 and 4.1 of theCustomer Insight for Retailplugin 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

Aforeign 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

Adelta 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" errorwhen connecting Aginity Workbench to Netezza 7.0.2.12.

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 SPUUtilization 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.

Minor

3780

Known Issues in Build 4.3.1864

Severity

Reference

Description

Workaround

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 databasewithout 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

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, select theDrop these entitiescheck box and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

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.

Run the script against the target schema.

Workaround 2:Generate two delta scripts

Open the source and target schemas in the Compare Schemas window.

Click the appropriateAlter Scriptbutton to initiate script generation.

In theGenerate Delta Script Optionswindow, underEntities to Script, clear theDrop these entitiescheck box to not drop any tables, and select appropriate check boxes underCreate these entitiesandModify these entities.

Save the generated script to a file.

Generate a delta script for the schemas again, selecting theDrop these entitiescheck box this time.

Save the script to another file.

First run the script file created in step 4 and then the one created in step 6.

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 SQLServer 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.

Documentation found here provides you with conceptual, procedural, and reference information to help you install and use the product and find answers to questions you may have about it.

Product Documentation

Aginity Enterprise Documentation

API Documentation

Aginity Enterprise API Documentation

Please visit our documentation page here.