Hi All, I have just made one enquiry and I am able to run execute enquiries, it is just taking 15 seconds to retrieve the records. Thank you very much to all. Currently i am doing the same way to other enquiries which has this problem.
Regards, Ramkumar.S On Mon, Nov 15, 2010 at 9:34 AM, Mohankumar Balasubramaniam < [email protected]> wrote: > Hi Ram, > > Please ensure that id should not contain more than 254 characters, which > also cause performance issue if it is Oracle DB(As of my knowledge). Try to > have id like TXN_TYPE*CO_CODE*DATE and write FT ids in it and read records > from actual local template. So that your selection will be easy. also move > your older records in template with extn .HIS, so file actual file size will > not be huge, if youy need those old datas then you can read .HIS file to get > the data. to create index on field use create-index command in jbase(use > this for ref : > http://www.jbase.com/r5/knowledgebase/manuals/3.0/30manpages/man/adv22_CREATE_INDEX.htm > ) > Do not create index for more than two fields for a file, which also create > performance issue. > > *please note: in Jbase @ID is indexed by default so have selection on id. > it would be better. > * > Regards, > Mohankumar B > On Sat, Nov 13, 2010 at 1:21 AM, Ramkumar Sreeni < > [email protected]> wrote: > >> Hi Jim, >> >> I meant to say 300 thousand records :), yes SSELECT takes more time than >> SELECT, but SSELECT is the one which run while we have input the file >> .FT.BMITPL.OTPASTS in the FILE.NAME <http://file.name/> field of enquiry. >> >> I just got one solution, that instead of selecting from the fields of the >> local template, i am writing all the information as part of @ID itself with >> '.' as delimiter and the SSELECT will be much faster I believe. >> >> How do i create index on a field, please help. >> >> Regards, >> Ramkumar.S >> >> On Fri, Nov 12, 2010 at 12:21 AM, Jim Idle <[email protected]>wrote: >> >>> Outside India, I doubt that too many people know what a lakh is! J >>> >>> >>> >>> However, why are you using SSELECT here? It will be a lot slower than >>> SELECT I suspect, especially when you come to use the list afterwards. I >>> think that you have just created a huge query without any indexes and lots >>> of conditions and it is going to take a long time to do that. Create some >>> indexes to help this. Maybe on CO.CODE for instance. >>> >>> >>> >>> Jim >>> >>> >>> >>> *From:* [email protected] [mailto:[email protected]] *On >>> Behalf Of *Ramkumar Sreeni >>> *Sent:* Thursday, November 11, 2010 3:46 AM >>> *To:* [email protected] >>> *Subject:* T24: Select on local template - performance issue >>> >>> >>> >>> Hi All, >>> >>> >>> >>> We created a report which will list the FT transactions that are with >>> TRANSACTION.TYPE LK OT..., for outward remittance report, so we created a >>> local template which will have the list of FT id's from the history file and >>> also fields which will store information like TRANSACTION.TYPE, CO.CODE and >>> 9 more fields as these fields are the same fields that will appear in the >>> enquiry dynamic select criteria, when we run the enquiry, internally the >>> enquiry is running a select criteria as shown in the mw42 jbase monitor >>> >>> >>> >>> SSELECT F.FT.BMITPL.OTPASTS WITH TRANSACTION.TYPE LIKE OT... AND CO.CODE >>> EQ BH0010001 etc >>> >>> >>> >>> The above select query is taking more time and the browser enquiry is >>> timing out, since the local template has 3 lakh records. >>> >>> >>> >>> Please suggest me a suitable solution so as to avoid browser enquiry >>> getting timed out. >>> >>> >>> >>> Regards, >>> >>> Ramkumar.S >>> >>> >>> >>> -- >>> Please read the posting guidelines at: >>> http://groups.google.com/group/jBASE/web/Posting%20Guidelines >>> >>> IMPORTANT: Type T24: at the start of the subject line for questions >>> specific to Globus/T24 >>> >>> To post, send email to [email protected] >>> To unsubscribe, send email to [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/jBASE?hl=en >>> >>> -- >>> Please read the posting guidelines at: >>> http://groups.google.com/group/jBASE/web/Posting%20Guidelines >>> >>> IMPORTANT: Type T24: at the start of the subject line for questions >>> specific to Globus/T24 >>> >>> To post, send email to [email protected] >>> To unsubscribe, send email to [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/jBASE?hl=en >>> >> >> -- >> Please read the posting guidelines at: >> http://groups.google.com/group/jBASE/web/Posting%20Guidelines >> >> IMPORTANT: Type T24: at the start of the subject line for questions >> specific to Globus/T24 >> >> To post, send email to [email protected] >> To unsubscribe, send email to [email protected] >> For more options, visit this group at >> http://groups.google.com/group/jBASE?hl=en >> > > -- > Please read the posting guidelines at: > http://groups.google.com/group/jBASE/web/Posting%20Guidelines > > IMPORTANT: Type T24: at the start of the subject line for questions > specific to Globus/T24 > > To post, send email to [email protected] > To unsubscribe, send email to [email protected] > For more options, visit this group at > http://groups.google.com/group/jBASE?hl=en > -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
