There are several reasons why networks are much slower than local disks
(think of SATA vs. Ethernet, SATA Bus vs. Network latency, no client
side caching etc.). This is especially true for random access patterns
like those SQLite uses.
So to minimize file access, (like already suggested by others) carefully
inspect and adjust your indexes using EXPLAIN and do a VACUUM and ANALYZE.
But in general I'd advise against using file-based databases over
network filesystems. They tend to have problems with random access
patterns. I've seen systems where you could happily throw gigabyte-sized
files back and forth but failing miserably on random access.
If you need server-side storage, consider using a full-fledged database
server. Since you are coming from Access, SQL Server Express comes to my
mind but PostgreSQL or Firebird may also be an option.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
