End_sql

Stupe · #1 (**permalink**) 04-23-06, 22:07

Hi gurus

Under my Business Objects documentation, there's a function that allows the usage of END_SQL (whatever that means), and its description:

Code:

For IBM DB2 databases, you can use the following:
END_SQL=FOR SELECT ONLY
The server will read blocks of data much faster.

I tried out the function, and what happened was this:

Code:

SELECT DISTINCT
  RTRIM(LU_STOCK.STOCK_ID)
FROM
  LU_STOCK
END_SQL=FOR SELECT ONLY

Ran it in a query tool, but that query doesn't work. Searched in Google, but couldn't find anything on this. How does this work?

Marcus_A · #2 (**permalink**) 04-23-06, 23:33

Try this:

SELECT DISTINCT
RTRIM(LU_STOCK.STOCK_ID)
FROM
LU_STOCK
FOR READ ONLY

Stupe · #3 (**permalink**) 04-24-06, 02:20

Marcus_A, much appreciated

grofaty · #4 (**permalink**) 04-25-06, 06:47

Hi,
but I don't bealive that FOR READ ONLY:
"The server will read blocks of data much faster."
Hope this helps,
Grofaty

sathyaram_s · #5 (**permalink**) 04-25-06, 07:09

Grofaty, I think FOR READ ONLY, the request becomes UNAMBIGUOUS and therefore data from the server is transferred to the client in BLOCKs rather than one row at a time, as in case of Updatable result sets ..

Sathyaram

grofaty · #6 (**permalink**) 04-25-06, 08:31

sathyaram_s,
I have tested several SQLs but no one had performance benefit from specifying FOR READ ONLY.
Grofaty

Internet Services

Web Development

Digital Marketing

Consumer Tech