Hi,
Elke wrote:
>>To optimize queries:
>>- good SQL (not necessarily the first idea how to query the wanted
result)
>>- useful indices/primary key-definition
>>- up-to-date update statistics values
>>are the only way to optimize queries in SAP DB
  Could you give me some guide lines on using "up-to-date update
statistics values".I assume this  can be done using the tuning tab on
dbmgui.However what estimate values should I use (or should I unselect
the 'use estimate values' option).Also what is the use for "select from
tables"/"Include update coloumns for marked tables". Is it possible to
optimize without the dbmgui?

Also in oracle I can store a single table on a separate physical device.
(Using oracles tablespace concept).Any parallel to this?

Thanks,
Ajit

        

-----Original Message-----
From: Zabach, Elke [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 24, 2003 7:36 PM
To: ajit_cus; [EMAIL PROTECTED]
Subject: RE: speeding up query execution on a single table

ajit_cus wrote:
> 
> Hi,
>  In oracle it is also possible to specify sizes of caches etc 
> associated
> with a table while creating it. Is there any parallel to this 
> in SAPDB.
> Is there a way to optimize execution of queries on a certain table or
> specify optimizations/parameters specifically for a table. 
> Thanks,

There is nothing in SAP DB like specifying cache for every single table.
The data cache can be used by any table up to its full size if no
other task/no other table needs some room resp. our table has
to give room to other data if that is needed by other tasks, for
intermediate or final results, meta-data.

To optimize queries:
- good SQL (not necessarily the first idea how to query the wanted
result)
- useful indices/primary key-definition
- up-to-date update statistics values
are the only way to optimize queries in SAP DB

Elke
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to