Hello,

Just a little help needed from the kind people who knows thoroughly
about ingres, so I can proceed with new dbms settings to empower an
Ingres Server.

4 quick questions :

1) Does set joinop timeout=100 means anything? (I thought this
instruction was just to switch on or of the optimizer timeout. In my
view, it doesn't accept duration)

2) Is there any difference whatsoever between the two statements:

set lockmode session where readlock=nolock;
and
set session isolation level read uncommitted

3) See a bunch of dbms parameter (and their corresponding values) on
some machine called sexp08ivbea (Windows 2003):

ii.sexp08ivbea.syscheck.dbms_segment 3 293 184
ii.sexp08ivbea.syscheck.dmf_seg_num 0
ii.sexp08ivbea.syscheck.dmf_segment 0
ii.sexp08ivbea.syscheck.rcp_segment 0
ii.sexp08ivbea.syscheck.segments 3

a) Are there any sort of limitation with the DBMS segment (here 3 Mo)
under Windows 2000? (MY fear is to reach something when resizing the DMF
Cache)

b) What are those other dmf and rcp segments parameters about?

4°) last, see:

ii.sexp08ivbea.syscheck.file_limit 414

- Is there any reason to try to change this when you raise the max
number of connections? (for me, this is unrelated)

Thank you very much for any answer.

P. Courant

At 12:37 AM +0200 9/9/2005, Patrick COURANT wrote:
It hardwires the timeout to N milliseconds. By the way, I don't think
there is an = in the syntax, although it might work either way.
set joinop [no]timeout [N]
is the way I remember it.

Yup. The second one puts your transaction into read-only mode as
well as turning off read-locking.


I'm not sure that these mean much. I'd have to double check, but I think
they are either informational for CBF display, or they are for syscheck
so that it validates that you have sufficient system resources.
I don't remember a "dbms_segment" at all.

No. It's also for syscheck validation.

Karl

Karl & Betty Schendel wrote:

Patrick