I'm trying to tweak performance on an R:Base X.5E order processing
system (> 2Gb ) with ~10 users.
We've been running with PAGELOCK ON; I'd like to set it OFF since most
of the SQL commands have WHERE clauses or are DECLARE CURSOR.
I want to update the RBase.DAT file to set PAGELOCK OFF with these SET
commands:
SET MULTI ON
SET STATICDB ON
SET VERIFY COLUMN
SET FASTLOCK ON
SET ROWLOCKS ON
SET PAGELOCK OFF
SET WAIT 4
SET INTERVAL 5
SET REFRESH 0
So I have some questions.
1) Is the order of the SET commands critical? I originally had ROWLOCKS
before FASTLOCk and R:Base was freezing up. Another developer suggested
the above sequence, putting FASTLOCK before ROWLOCKS.
2) PAGELOCK replaced some of the function of QUALCOLS starting in
version X; What should be the correct QUALCOLS value if I use the above
SETs? (Client does not [currently] SATTACH to other data sources)
3) If a row of data is being updated, does that slow down read-only
performance, especially if PAGELOCK is on? e.g. SEL COUNT(Column) FROM
table
I welcome any other suggestions.
I would test the above but client has been very patient. I don't want
to cause any more anomalies than necessary.
Thanks and Happy Easter
Doug
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/87695ee0-de9b-10ec-3bbb-4e51fbda7f01%40wi.rr.com.
