Skip to Content

Processing time in HANA SQL console

Hi,

when executing an SQL statement in the SQL console of the HANA studio, this kind of message is returned:

Statement 'select * from "_SYS_BIC"."kul.dm.fi.proc.kbh/CV_YFR012" WHERE ( ( ...'

successfully executed in 10.933 seconds (server processing time: 10.921 seconds)

Fetched 1000 row(s) in 437 ms 944 µs (server processing time: 8 ms 540 µs)

Result limited to 1000 row(s) due to value configured in the Preferences

Can I find out somehow how the time-consumption of this statement is composed.

We get almost the same time no matter how big the result of the statement (8 records, 300 or 140.000 last the same number of seconds). The view we call contains an attribute view and an analytical view.

How can we analyze this?

Thanks for any info.

Regards.

Kris

Message was edited by: Tom Flanagan

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Jul 08, 2014 at 02:24 PM

    What we found out ourselves:

    In the SQL-console you can right-click on the statement and select Visualize Plan. If you execute this you can detect rather precisely where the biggest time consumption lies..

    So far so good.

    Kris

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 25, 2014 at 12:40 PM

    Hi Kris,

    Statement 'select * from "_SYS_BIC"."kul.dm.fi.proc.kbh/CV_YFR012" WHERE ( ( ...'

    successfully executed in 10.933 seconds (server processing time: 10.921 seconds)

    This time shows total time taken by HANA to run the query and fetch all the results

    Fetched 1000 row(s) in 437 ms 944 µs (server processing time: 8 ms 540 µs)

    This Time shows that once the whole result was fetched it took HANA 437 ms to show first 1000 rows.

    If you want to know how the Query got executed and time taken in each step, then write the SQL query in SQL console and  R-Click on it and select Plan Visualisation.

    Using this tool you can get the breakdown of query and can see - how the query was executed, how many records were fetched by the query in each step

    and how much time was taken in processing each step

    Regards,

    Vivek

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 25, 2014 at 01:21 PM

    Hi Kris

    when you look at the fetch time, you of course should get more or less the same timing whenever you fetch the same amount of data.

    It's the time required to move data from the server to your client. So unless the network connection speed really varies a lot this number should be somewhat stable.

    However, I recommend to check the server processing time in the "statement executed" line. That usually provides a much better feeling on relative performance differences.

    - Lars

    Add comment
    10|10000 characters needed characters exceeded