When I submit Redshift queries using Toad 6.2/6.4, windows, once it appears the query is complete Toad will lock up waiting for the "Messages" to be returned preventing me from accessing the editor window. Once 'Messages' are returned Toad will unlock and I can access the editor again. We've tested this using multiple ODBC drivers, 2.1.3 and above with SAML.
According to AWS(see below) the query we tested ran almost immediately but returning the results back to the Message window can take up to a minute give or take. We tested a simple query, "drop table if exists junk;"
From AWS:
From our side, we verified logs and can confirm that driver returned SQL_SUCCESS almost immediately. [DEBUG] 2025-04-23 14:53:45.046 [ODBCAPI:rstrace.h:96] [19988] SQLExecDirectW( phstmt=0x00000224A1462FD0 pwCmd=drop table if exists junktable cchLen=SQL_NTS )
[INFO] 2025-04-23 14:53:45.046 [RSUTIL:rsutil.c:12534] [19988] Skiping results for streaming cursor... [INFO] 2025-04-23 14:53:45.046 [RSUTIL:rsutil.c:12542] [19988] Skiping results for streaming cursor done [DEBUG] 2025-04-23 14:53:45.128 [ODBCAPI:rstrace.h:96] [19988] SQLExecDirectW() return SQL_SUCCESS Note the last line in above logs: [DEBUG] 2025-04-23 14:53:45.128 [ODBCAPI:rstrace.h:96] [19988] SQLExecDirectW() return SQL_SUCCESS Driver returned SQL_SUCCESS within milliseconds.
Anyone else experience this/have an idea on how this can be corrected? Toad, ODBC or Windows setting?
Thanks