Re: [sqlite] Using SQLite on networked drive
Thomas It is not safe to use SQLite on networked drive because of file locking problems and how OS caching takes place. Please refer answers by DRH above as well as in other question-answers. Different OS have different file locking and caching mechanism. Probably Windows 2000 might have suitable one to what SQLite database needs. That is why I asked about if any one has idea/experience of sharing SQLite database by multi-users while file is on Windows 2000 (in perticular). Regarding sharing MS Access database file: You should not keep database file on Windows 95 / 98 / (ME) file share but keep it on Windows NT/2000. In some MSDN articles, microsoft recommends about sharing MS Access database : - Do not keep database file on Windows 95 / 98 / (ME) file share - Store the database file and that you share the database file on a Windows NT server or on Windows 2000 server with opportunistic locking disabled. Please refer (Knowlegde Base Articles) -> How to keep a Jet 4.0 database in top working condition. -> How To Synchronize Writes and Reads with the Jet OLE DB Provider and ADO -> How To Synchronizing Reads and Writes Between Two DAO Processes Especially refere to topic, "Issues to consider when you share a Microsoft Jet database" Rohit -- View this message in context: http://www.nabble.com/Using-SQLite-on-networked-drive-tf1213767.html#a6499937 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Using SQLite on networked drive
RohitPatel wrote: I have read articles and understood that it is not safe to access SQLite database file on network drive. (on all windows). But what about Windows 2000 (Server) ??? i.e. If SQLite (3.3.4 or 3.3.6) database file resides on disk drive of Windows 2000 Server, then is it safe to access that SQLite database via network ? Any thoughts...Any one's experience ? Thanks for any help. Rohit It is safe to access an Sqlite file across a network. Where you have to be careful is multiple users and locking across a network. You should also be aware that performance will suffer if the file is accessed across a netwrok for simple bandwidth reasons. If you are setting up a multi-user, multi workstation DBMS Sqlite may not be your best choice. If you have an embedded DBMS then Sqlite is an excellent choice. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Using SQLite on networked drive
On Mon, 25 Sep 2006 11:22:41 -0700 (PDT), you wrote: Hello >I have read articles and understood that it is not safe to access SQLite >database file on network drive. (on all windows). > >But what about Windows 2000 (Server) ??? i.e. If SQLite (3.3.4 or 3.3.6) >database file resides on disk drive of Windows 2000 Server, then is it safe >to access that SQLite database via network ? Now I'm totally confused.. ;-) You say, it is not safe to store DB on Network, but it is safe to store it on a Server. Where you see that this is different? It seems to me, that you mean, it is generally unsafe to store the DB in a Network-Drive. Is this thus? You can store a DB on your local Machine, or you can store a DB on Network-Drive, like as Windows Server. The SQLite-DB remains a Flatfile so or so, in contrast to a Client-Server-based System. If you store the DB on Network with possibly concurrency users, you have to set users rights with needed permits in the networks OS. And you have to avoid the logical collisions within your App, if more than one User try to write the same Record. I think, there a no serious problems in a dialog-based and interactive application in Network with some concurrent writing users and some more reading users. >Any thoughts...Any one's experience ? As additional compare, MS Access is a Flatfile-DB too. but it is only safe and stable until max 5 Users. That's my experience. I think, SQLite limits are much higher. *hmmm* If you create a real big application with many Users, maybe you think about again and anymore, which DB is the best ;-) HTH Thomas - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Using SQLite on networked drive
I have read articles and understood that it is not safe to access SQLite database file on network drive. (on all windows). But what about Windows 2000 (Server) ??? i.e. If SQLite (3.3.4 or 3.3.6) database file resides on disk drive of Windows 2000 Server, then is it safe to access that SQLite database via network ? Any thoughts...Any one's experience ? Thanks for any help. Rohit -- View this message in context: http://www.nabble.com/Using-SQLite-on-networked-drive-tf1213767.html#a6492384 Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Using SQLite on networked drive
Deepak , I simply got it done by maping the shared folder to a drive letter and made the connection persistant. Moreover changed all the inherent script was also changed in php cli program and every this is rocking Best Regards, Vishal Kashyap. http://vishal.net.in On 3/3/06, Deepak Kaul <[EMAIL PROTECTED]> wrote: > I was tasked to use sqlite on a NFS mount on MacOSX 10.4. I had > numerous problems with it because MacOSX does not implement locks > properly. It would run for about 15 minutes or so and then I would > start receiving Database Malformed errors. I had to come up with a > different solution. > > I came up with a scheme where only one process would handle updating the > database directly. All other processes locally or remotely would update > the database through a file hand shaking protocol. > > Here is an example > Database Updater Process (Server) > Database Client Process (Client) > > Server defines two directories (queries and responses). > > Client wants to insert, update or delete data from a database. > 1. client creates a file with the necessary information > 2. client moves file into queries directory > 3. server sees new file in queries directory > 4. server parses file > 5. server inserts, updates or deletes data from database. > > Client wants to select data from a database. > 1. client creates a file with the appropriate sql statement > 2. client moves file into queries directory > 3. server sees new file in queries directory > 4. server parses file > 5. server preforms select statement > 6. server creates response file > 7. server moves response file into response directory > 8. client sees new response file in response directory > 9. client parses file > 10. client obtains data > > This scheme is preferred over sockets because if the database updater > process dies you won't lose information. All inserts, updates and > deletes will be sitting in the queries directory waiting for the > database updater process to start again. > > This is just one solution to work around the NFS problem I was having. > If you find NFS does not work for you I would try either some sort of > sockets implementation or some sort of file hand shaking protocol. > > Vishal Kashyap wrote: > > >Dear Ray , > > > > > > > >>I would be interested in knowing how you handle simulatneous inserts and/or > >>updates... > >> > >> > > > >Their is a possibility of simultaneous selects thats all. Moreover the > >shared drive would be mapped > > > > > >-- > >With Best Regards, > >Vishal Kashyap. > >http://www.vishal.net.in > > > > > > > > > > -- > Software Engineer > [EMAIL PROTECTED] > 301.286.7951 > -- With Best Regards, Vishal Kashyap. http://www.vishal.net.in
Re: [sqlite] Using SQLite on networked drive
Deepak Kaul said: > I was tasked to use sqlite on a NFS mount on MacOSX 10.4. I had > numerous problems with it because MacOSX does not implement locks > properly. It would run for about 15 minutes or so and then I would > start receiving Database Malformed errors. I had to come up with a > different solution. > > I came up with a scheme where only one process would handle updating the > database directly. All other processes locally or remotely would update > the database through a file hand shaking protocol. This is pretty ingenious, but I really think that in a situation like this you'd be better off looking at something like PostgreSQL, that can handle multiple network clients. SQLite is a great tool, but it's not the only tool. Use the right tool for the job, and a file-based database is rarely the right tool when network access is needed. Clay Dowling -- Simple Content Management http://www.ceamus.com
Re: [sqlite] Using SQLite on networked drive
I was tasked to use sqlite on a NFS mount on MacOSX 10.4. I had numerous problems with it because MacOSX does not implement locks properly. It would run for about 15 minutes or so and then I would start receiving Database Malformed errors. I had to come up with a different solution. I came up with a scheme where only one process would handle updating the database directly. All other processes locally or remotely would update the database through a file hand shaking protocol. Here is an example Database Updater Process (Server) Database Client Process (Client) Server defines two directories (queries and responses). Client wants to insert, update or delete data from a database. 1. client creates a file with the necessary information 2. client moves file into queries directory 3. server sees new file in queries directory 4. server parses file 5. server inserts, updates or deletes data from database. Client wants to select data from a database. 1. client creates a file with the appropriate sql statement 2. client moves file into queries directory 3. server sees new file in queries directory 4. server parses file 5. server preforms select statement 6. server creates response file 7. server moves response file into response directory 8. client sees new response file in response directory 9. client parses file 10. client obtains data This scheme is preferred over sockets because if the database updater process dies you won't lose information. All inserts, updates and deletes will be sitting in the queries directory waiting for the database updater process to start again. This is just one solution to work around the NFS problem I was having. If you find NFS does not work for you I would try either some sort of sockets implementation or some sort of file hand shaking protocol. Vishal Kashyap wrote: Dear Ray , I would be interested in knowing how you handle simulatneous inserts and/or updates... Their is a possibility of simultaneous selects thats all. Moreover the shared drive would be mapped -- With Best Regards, Vishal Kashyap. http://www.vishal.net.in -- Software Engineer [EMAIL PROTECTED] 301.286.7951
Re: [sqlite] Using SQLite on networked drive
Just out of personal interest: Could you detail on which versions of Windows it works, and on which it doesn't? Thanks Rolf [EMAIL PROTECTED] wrote: "Jay Sprenkle" <[EMAIL PROTECTED]> wrote: On 3/2/06, Vishal Kashyap <[EMAIL PROTECTED]> wrote: Dear All , Wanted to know if we can use sqlite database from network drives ? It works if your operating system correctly handles locking. If I remember correctly there are some problems with windows drives, but NFS works. Check the documentation section of the web site. . It works on some, but not all, versions of windows. And it works on some, but not all, version of NFS. On those operating systems where network file locking is not implemented correctly the result will be corrupt database files. The performance of SQLite over a network filesystem is consistent to the performance of the network filesystem itself - very slow. SQLite will, in theory, work over a network filesystem. But for the reasons cited above, it is not recommended. That said, I should add that for the reasons cited above, the use of a network filesystem itself is not recommended. But that is a whole other story -- D. Richard Hipp <[EMAIL PROTECTED]>
Re: [sqlite] Using SQLite on networked drive
"Jay Sprenkle" <[EMAIL PROTECTED]> wrote: > On 3/2/06, Vishal Kashyap <[EMAIL PROTECTED]> wrote: > > Dear All , > > > > Wanted to know if we can use sqlite database from network drives ? > > It works if your operating system correctly handles locking. > If I remember correctly there are some problems with windows drives, > but NFS works. > Check the documentation section of the web site. > > . It works on some, but not all, versions of windows. And it works on some, but not all, version of NFS. On those operating systems where network file locking is not implemented correctly the result will be corrupt database files. The performance of SQLite over a network filesystem is consistent to the performance of the network filesystem itself - very slow. SQLite will, in theory, work over a network filesystem. But for the reasons cited above, it is not recommended. That said, I should add that for the reasons cited above, the use of a network filesystem itself is not recommended. But that is a whole other story -- D. Richard Hipp <[EMAIL PROTECTED]>
Re: [sqlite] Using SQLite on networked drive
On 3/2/06, Vishal Kashyap <[EMAIL PROTECTED]> wrote: > Dear All , > > Wanted to know if we can use sqlite database from network drives ? It works if your operating system correctly handles locking. If I remember correctly there are some problems with windows drives, but NFS works. Check the documentation section of the web site.
Re: [sqlite] Using SQLite on networked drive
I would be interested in knowing how you handle simulatneous inserts and/or updates... On 3/2/06, Vishal Kashyap <[EMAIL PROTECTED]> wrote: > > Dear All , > > Wanted to know if we can use sqlite database from network drives ? > > -- > With Best Regards, > Vishal Kashyap. > http://www.vishal.net.in > -- Ray Mosley
[sqlite] Using SQLite on networked drive
Dear All , Wanted to know if we can use sqlite database from network drives ? -- With Best Regards, Vishal Kashyap. http://www.vishal.net.in
