It's not going to speed everything up, just certain select statements. And quite honestly, it's going to speed up certain select statements that are not really kosher.
For example, if your application is full of select statements like SELECT FILE WITH @ID = "ABCDEF", then you should probably re-write the statement to something like SELECT FILE "ABCDEF". If you can't do that, because you don't have the source, don't have the time or whatever, then creating the index might help. I first heard of this a few years ago and yes, it does work, but I've never actually used it in a live application. It's just not a real good use of an index file. ----- Original Message ----- From: "jjuser ud2" <jju...@gmail.com> To: <u2-users@listserver.u2ug.org> Sent: Wednesday, January 28, 2009 1:06 PM Subject: [U2][UD] Index for @ID (IBM documentation) > Hi everybody, > > In the IBM publication "Developing UniBasic Applications", Version > 7.1, December 2006, it says on page 4-16 (page 93 in my PDF file): > > Tip: Create an index for @ID to speed access to data > records. > > Seriously? Will that honestly speed things up in a file that has > eight million records? > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ [demime 1.01d removed an attachment of type application/pgp-signature which had a name of PGP.sig] ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
