<[EMAIL PROTECTED]> writes: > > Hello Mike, > > Did you say that the PRAMGA locking_mode=EXCLUSIVE was set ? > The doc suggests this speeds things up ... > > I have that set, yes. > > You are not clear about which aspect is slow - are you already using > sqlite3_bind_x() and placeholders (?) in your SQL statements ? > Doing a sqlite3_prepare every time you do a query can slow things > down. > > I am using the sqlite.exe command line executable in a separate thread to query my database. I don't have > code level control over the access to it. > > I was thus wondering if there is anything i can do on a query level (as input to the command line executable) to > speed things up. > > Any help is much appreciated, > > christophe Leske >
When you say 'sqlite.exe' I presume you are referring to 'sqlite3.exe' ? (http://www.sqlite.org/sqlite.html) If not, update your software ! Using the correct INDEX can speed queries up vastly, so if you can identify how you are accessing the data, and then set that/those columns as INDEXed, that will help ... http://www.sqlite.org/lang_createindex.html Best choice for index could be a) field that directly identifies record, eg. serial number b) field that allows quick rejection of most non-matching records, reducing amount of data to search by other methods, eg. surname Of course, creating an index uses more space in the DB, so there is always a tradeoff. (Techie note http://20bits.com/2008/05/13/interview-questions-database-indexes/) MikeW _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
