Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread Statement Logging
Mon, May 20 2019 1:56 PMPermanent Link

Kevin Koehne

I'm trying out the ENABLE STATEMENT LOGGING feature and I'm finding that long running SCRIPTs are not being logged. Is that the case or am I missing something?
I am using version 2.31 Build 4.
Thanks,
Kevin
Mon, May 20 2019 2:02 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Kevin,

<< I'm trying out the ENABLE STATEMENT LOGGING feature and I'm finding that long running SCRIPTs are not being logged. Is that the case or am I missing something? >>

Yes, the statement logging only applies to individual SQL statements, not to scripts.

Tim Young
Elevate Software
www.elevatesoft.com
Mon, May 20 2019 2:03 PMPermanent Link

Kevin Koehne

Thanks Tim. Any chance we can get scripts included in the future? Or are individual statements in scripts logged?
Mon, May 20 2019 2:09 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Kevin,

<< Thanks Tim. Any chance we can get scripts included in the future? Or are individual statements in scripts logged? >>

The individual statements in the script are logged, and it is assumed that the rest is easily-diagnosed.

The reason why statements are log-able in the first place is because the query optimizer could potentially make bad decisions, or the data could grow and result in statements that no longer work well within a given timeframe.

Tim Young
Elevate Software
www.elevatesoft.com
Mon, May 20 2019 2:26 PMPermanent Link

Kevin Koehne

Tim,
I just tried a quick test. Ran a 'slow query', which got logged as expected. I took the same query and stuck it in a script, (e.g. Execute Immediate 'slow query') and in that case, the query was not logged.
Thanks,
Kevin
Sat, May 25 2019 2:49 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Kevin,

<< I just tried a quick test. Ran a 'slow query', which got logged as expected. I took the same query and stuck it in a script, (e.g. Execute Immediate 'slow query') and in that case, the query was not logged. >>

Yes, you're correct - the script progress is effectively "hiding" the execution time for the query because EDB isn't interested in the individual query execution times in a script (at least not from the standpoint of the overall elapsed time for the script).

I'm going to need to add a new layer of progress updating to the query execution in the scripts, and this will be fixed in the next 2.3` build 5.

Tim Young
Elevate Software
www.elevatesoft.com
Sat, May 25 2019 2:50 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com


<< fixed in the next 2.3` build 5. >>

Sorry, typo - 2.31 Build 5.

Tim Young
Elevate Software
www.elevatesoft.com
Tue, May 28 2019 11:42 AMPermanent Link

Kevin Koehne

Thanks Tim!
Image