Hi Francine - There is another issue that one of the user is facing. When the user tries to execute multiple statements in the Teradata Studio by right clicking and selecting 'Execute as Individual statements'. It just does not create a history entry, however the history entry is created when he right clicks and selects 'Execute as single statement'. The other thing is we tried enabling LOG = DEBUG to capture any logs , when the history entry is not created. Strangely the logs are also not created. Could this be due to some preference (History not getting saved when multiple statements are highlighted and executed as individual statements)? Can you clarify ?
@Roopalini, Execute as Individual statements will create an entry in the SQL History. What type of statement are you executing? New entries appear at the top of the table. Is a filter set to filter it out? Setting LOG=DEBUG as a JDBC Property will turn debug logging on for the JDBC Driver. If you want to turn on debug logging for Teradata Studio, follow the instructions in the Help. From the top level tool bar, choose Help>Help Content. Open the Teradata Studio help book and go to Troubleshooting. You don't need to add any of the components to the list, just set the Datatools logging level to DEBUG and Console Display Logging Filter to DEBUG. Also open the Console View and set to Teradata Log Console to see the output.
Thanks for the prompt response Francine!! The statements are simple select with a wrong column name. Could you let me know where the filter is set to filter it out? I shall have the user enable the debug and check if we are able to nail down the issue Thanks Roopalini