I find that it's best not to generalize. I'd suggest trying it in tests both ways and testing the times! Then let us know what you found out!
David Blocker ----- Original Message ----- From: "Jim Limburg" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, September 09, 2003 4:04 PM Subject: [RBASE-L] - RBG65 - To Project of not to Project > G-Day all > > Which situation by you all's experience would be faster. I have a table > which had about 30 columns, most of which are small - integers,1-8 size > in text and so on. One of the columns is text 100. This table has about > 80,000 rows in it. The text 100 column is indexed, but searching is somewhat > slow. The table has a PK - integer. Would it be faster to project a > temp table to a user who searches if frequently, of just the PK and the > text 100 column. The user who does this searching wouldn't need it updated > each time. I could put a refresh data button on to reload the temp table, > so the user could do that a few times a day. > > Or is it just faster to search on the table that has the 30 columns. I > know indexing is suppose to "put things in ram" so to speak, or at least > that's how I've figured it, so I'm not sure at this point what would be > best. I'm curious to find out some of you guru's findings in areas like > this. > > Jim Limburg > >
