Michael,
I may be incorrect, but I believe we should be looking at the QualCols as a multi user setting, not so much as a speed setting. I.E. The default is 10. (Which overall, provides the fastest UPDATE response. I am unsure, but I do not believe that append or insert is effected at all by QUAL) QUAL 2 does not improve speed in any setting.... it helps avoid access conflicts. In a sense, QUAL 2 never improves speed. The only reason you would change to 2 is if a large number of users would be accessing data for UPDATES (look ups are not effected) that would commonly reside in the same page of memory. Remember, the speed of an update on a single record using an indexed where clause would not be effected by either 10 or 2 setting. So more to the point, the amount of data being updated ( 1 record or many) is not the logic to decide if QUAL 10 or 2 should be used. The deciding factor is multi user environment... If updating conflict is not an issue, one would almost always use QUAL 10. If updating conflict is an issue, the QUAL 2 would be set. To answer your specific question, yes you can change the QUAL value at any time. However, remember that while the setting is session specific, it's effect is global. If user 1 sets QUAL 10 and peforms an update, it will place record locks on the table a page of memory at a time. (I am unsure how to calculate how many records might be in a page memory of data) Even if user 2 has QUAL 2 set, the record locks from user 1 are still in effect and user 2 will be locked out of any records in the page of memory being updated by user 1! -Bob ----- Original Message ----- From: "Michael J. Sinclair" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Wednesday, November 4, 2009 9:19:51 AM GMT -06:00 US/Canada Central Subject: [RBASE-L] - Re: SET FASTLOCK ON (was Re: Qualcols 2 vs 10) Can QualCols be changed prior to each update/insert/append? If so, could I set QualCols to 2 for updating/inserting/appending 1 or 2 rows, and set to 10 for many rows? Mike -------------- Original message from "A. Razzak Memon" <[email protected]>: -------------- > At 09:12 AM 11/4/2009, Karen Tellef wrote: > > >Not sure how fastlock works, but you would have to disconnect the > >database if you were required to turn staticdb on and you normally > >have it off (I think only one of my clients has staticdb on). > > FYI ... > > FASTLOCK, along with STATICDB, MULTI, and TRANSACT settings MUST > match for all users connected to a database and must be set before > a database is connected. > > FASTLOCK cannot be set ON unless STATICDB is ON. > > If you SET FASTLOCK ON and connect the database, but STATICDB is > OFF, after connecting to the database FASTLOCK is turned OFF. > > Try these settings and see what you learn from the power of R:BASE! > > Very Best R:egards, > > Razzak. > >
