On May 8, 2019, at 8:42 AM, Andrew Moss <curioussq...@googlemail.com> wrote: > > We are currently backed into a corner by a customer
In what way, exactly? It might help to know. > and are looking at > using an SQLite database hosted on a windows network share (using server > 2012 R2 or later). You’ve fallen victim to the XY Problem: http://xyproblem.info/ You’ll get more solutions if you don’t unnecessarily constrain the solution space in the way you ask the question. > We are well aware this is not advisable and have read > https://www.sqlite.org/whentouse.html. The first drafts of that page were written using an ink compounded from lost data and bitter tears. You almost certainly have insufficient cause to disregard its advice. > Any notes from other users who had to do something similar in the past? How about you give up on the idea of using Windows shares to distribute a SQLite DB and use a tool meant for the job, such as BedrockDB? https://bedrockdb.com/ For a single-server application, you can just pass it -serverHost and then convert all of your sqlite3_execute() and similar calls to HTTP POST calls to BedockDB. This transition will be a slog, but once you’ve completed it, you’ve got a distributed DBMS that’ll let you go beyond multiple hosts to create caching schemes, replication, failover, etc. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
