DRH, To be completely honest, the first implementation of my project is completed. I'm in the fine tuning stages, given the small amount of time that I have available. But, it was easier to pose the questions about the best way to do this as if the project had not been implemented yet.
I already have all 3 fields indexed because searches are performed on all 3 fields: individually and in combination, and that is my prior training. However, I was wondering if I made a mistake by indexing the fields, since the indexes and the data are identical. I am a little short on time. My employer doesn't believe stress testing, load testing, nor optimization are important because my employer has no experience with databases. I have repeatedly explained that database optimization is an art, not a science, and all databases and the applications that access them require testing and refinement. No one is listening. I was hoping to make an intelligent choice without taking the time to test it one way, then the other because I am probably not going to be given that time. I agree with everything you said. If I never get the time to test my applications both ways (indexed, not indexed), can you make a best recommendation? Lee ____________________ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, March 14, 2008 3:53 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Efficiency Question - Value Or Liability for Indexingof This Table? "Lee Crain" <[EMAIL PROTECTED]> wrote: > I am debating the performance gains to be realized, if any, by indexing a > particular table in a system implementation for which I am responsible. > You are getting way ahead of yourself. Stop trying to speculate about whether or not an index or indices will be useful. Write your application first. Then test it. Measure the speed. Then add an index and test and measure again. Compare the measurements. Add a different index or combination indices. Repeat until done. Premature optimization leads to bad design. Build your application first, then measure it to see where optimization is needed. -- D. Richard Hipp <[EMAIL PROTECTED]> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
