Organization Name

Verizon

Description

We would like to request the following enhancements to the SQL Editor in OAS data set creation.

1. Show clearer and more actionable error messages, including column name or syntanx that caused the error. Current error messages are non-descript which makes it hard to decipher the cause of the errors, especially when the SQL is accurately written and works using other editors like Toad or SQL Developer.
2. Add "Validate" option before previewing data/ creating data set.
3. Enable the ability to "pass-through" queries to allow users to execute SQLs directly against the external database (Oracle, Tableau, SQL Server, etc). This would enable database-specific SQL syntaxes to work in OAS SQL editor and not generate error messages. 
4. Allow special formatting - space, carriage returns, tabs, etc. This would enable users to simply copy SQLs written  in other editors like Toad or SQL Developer and paste in OAS SQL Editor. Current editor is too sensitive that users have to format their SQLs to remove carriage returns, tabs for them to work.  

Use Case and Business Need

Our users are asking for better SQL editors when creating data sets in OAS. Current SQL Editor does not provide clear error messages, is very sensitive, and generate errors even when using accurately written SQLs. Users are having to format their SQLs to remove carriage returns, tabs, spaces, etc. for the SQLs to work which is not very ideal.

Original Idea Number: a462dbf7f5