Coginiti menu Coginiti menu

Coginiti September 2021 Update (v21.9) Release Now Available

Chris Crompton
September 8, 2021

Coginiti 21.9 release features several helpful updates, including expanded EXPLAIN plan coverage for Amazon Redshift and Snowflake, quick role switching for Snowflake connections, and increased databased object visibility for Greenplum and Postgres. View release overview demo.

Explain Plan for RedShift & Snowflake

Explain plan is an indispensable tool for query performance tuning. Prepending your SQL query with “EXPLAIN” replaces normal result output with under-the-hood information revealing the steps, joins, and indexes utilized in the execution of the particular query.  Very useful data, though the standard row/column query execution plan output can be pretty difficult to decipher.

Coginiti makes your job easier with our “Explain Plan” query execution option which presents this output in a hierarchical, easy-to-read format.  This feature was previously exclusive to Db2, but our 21.9 release extends our Explain Plan support to Amazon Redshift and Snowflake.  You can find this function by clicking the downward arrow beside the main “Run Script” button.

Snowflake Role Switching

Great news for our large Snowflake database community.  You can now switch between user roles directly in the Query Editor window!  Your default role is still set at the connection level, but Coginiti users now have a simple option to run queries under a more restrictive role which provides an extra degree of data protection.

Database Object Coverage

We’re always working hard to expand object, autocomplete and DDL coverage for our supported database platforms. Here’s what we’ve added in version 21.9:

  • Greenplum – Referenced by, Foreign Key
  • Postgres – Referenced by, Foreign Key

 

Over 15 bug fixes and application performance improvements.

  • Discovery doesn’t search special characters such as ‘_’ correctly
  • Database filtering issue with deleted connections
  • “Hide unnecessary nodes” setting doesn’t work on AzureSQL database

Until next time…. Query on!