I tried to enable this feature out of curiosity, but depending on the number of columns returned, it takes several seconds before the Data Grid is shown after executing a query.
Are you aware of this, can you reproduce it?
I tried to enable this feature out of curiosity, but depending on the number of columns returned, it takes several seconds before the Data Grid is shown after executing a query.
Are you aware of this, can you reproduce it?
Hi Peter,
Are you saying this is noticeably slower with this option turned on than the same query executed with the option turned off? How many columns are you trying to return from your query? Or, do you have a sample script that you could e-mail me offline?
-John
Yes. I tried it with this query after enabling DBMS Output and Spool SQL:
SELECT * FROM user_tab_cols WHERE 1 = 2;
Without Sensitive Data Awareness dbms_output is evaluated after ~100ms:
----------------------------------
-- Session: ###
-- Timestamp: 07:09:32.815
SELECT * FROM user_tab_cols WHERE 1 = 2;
----------------------------------
-- Session: ###
-- Timestamp: 07:09:32.924
DECLARE
v_lines SYS.DBMS_OUTPUT.chararr;
...
With Sensitive Data Awareness it takes almost two seconds until results are displayed (Statement processing dialog disappears immediately though):
----------------------------------
-- Session: ###
-- Timestamp: 07:09:47.649
SELECT * FROM user_tab_cols WHERE 1 = 2;
----------------------------------
-- Session: ###
-- Timestamp: 07:09:49.441
DECLARE
v_lines SYS.DBMS_OUTPUT.chararr;
...
This view has more columns, so it takes longer:
----------------------------------
-- Session: ###
-- Timestamp: 07:15:04.284
SELECT * FROM v$active_session_history WHERE 1 = 2;
----------------------------------
-- Session: ###
-- Timestamp: 07:15:09.135
DECLARE
v_lines SYS.DBMS_OUTPUT.chararr;
...
Hi Peter,
I was able to reproduce this issue with the examples you provided. I've logged this as a bug so it can be fixed. I'll let you know when it's finished.
Thanks for letting us know about this!
-John
Hey Peter,
This has been fixed for the first beta when it's released. Thanks again for letting us know about this issue!
-John
Your're welcome, thanks for looking into it.