System.Data.SQLite

Benifits of logging to DB are SQL's filtering capabilities, here log file is written along with large number of flags like possible error/exception type, module name etc so it is easier (and faster) to simply write where clause and filter out the results. Also there should be no (or min) difference between a write and subsequent read. This ...

There are times when a person just wants to pull out all his hair and give UP! Man i have tried so much and most of it is futile. I understand what you are saying is correct and also that DataReader doesnt support disconnected interface and it boils down that i have to use datasets, if i want multi threaded access on a in-memory database. Adding ...

Hello... For quite some time now i have been trying to find ways to get maximum possible performance out of SQLite in my application. Here is the configuration of SQLite I am using, for benchmarking (Till now the road has been quite bumpy and it will be great if anyone has any idea about how to resolve it). Data source is set to ...

I have been working on these lines and i have a small problem. I am not able to comprehend this INSERT INTO mymaintable SELECT * FROM temp.mytemptable; DELETE FROM temp.mytemptable; I have created two SQLiteConnections memoryCon and diskCon and inserting in memory one and reading from diskCon. but i dont know how to get data from memory db and ...

Can a in-memory table created in one thread accessed from another thread. I tried doing it and exceptions tell me its not. Can any one conform this? Thanx

Ok. So it boils down to that if ACID is not what is required then Access is better suited than SQLite? Anyways i will try keeping memory tables for inserts and sync-ing them to disk for selects and see if it has a better performance and fault tolerance than Access. I will post my results in benchmark section.   Thanx

Ok about the page size, it was one of my desparate and illogical attemps to get things speeded up. And on transaction inside while loops, the reason I am doing it is because in the real application where SQLite is going to be used, there is one thread that is getting data packets from internet in a arbitrary way and is inserting them in the ...

Thank you for replying so fast. No actually I am not inserting 1 row and comparing speed. Actually its quite the contrary. Here is what i am doing - Make two databases one of access and other of SQLite Start two threads on these databases (with independent connection objects). One thread for insert and other for selects. Measure time taken ...

hello all I have been benchmarking SQLite with Access 2003 lately and have found some very problems with SQLite/ADO.NET wrapper or hopefully the way I am doing it is wrong. Here is the code in question: SQLite code: slTransaction = slConnection.BeginTransaction slCmdInsert.ExecuteNonQuery() slTransaction.Commit() Access ...