Thanks, Razzak, for the additional info. I believe I do have some places where switching QUALCOLS to 10 when doing updates will be helpful. It is good to know we can do this in code to improve performance when appropriate,
Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Tuesday, February 26, 2013 1:15 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Tip of the Day: Optimizing R:BASEMulti-UserEnvironment At 01:41 PM 2/26/2013, Dennis McGrath wrote: >Thanks Razzak, > >I've got a couple of questions. > >1. Does QUALCOLS have any effect on TEMP tables? >I have many places where I do massive updates on temp tables and >wonder if this would help avoid the I/O errors associated with this. > >2. Does QUALCOLS have any effect when INSERTing many rows in either >a temp or permanent table? Dennis, Technically, all TEMPORARY Tables/Views and defined SCRATCH settings are session specific (local session of R:BASE). Thus, no effect on stand-alone, session specific TEMPorary tables. TEMPorary tables are NOT shared nor visible to another user or session of R:BASE in a multi-user environment. As INSERTing rows does not affect the table lock, thus QUALCOLS should have no effect on temporary or permanent tables. However, INSERTing rows will be affected by PK/FK/UK and number of INDEXes (if defined) on a given table. QUALCOLS settings along with STATICDB ON and FASTLOCK ON are most efficient and fastest method when you are doing an UPDATE and/or DELETE affecting many rows in a table. Hope that helps! Very Best R:egards, Razzak. www.rbase.com www.facebook.com/rbase
