Sqlite Caching problem

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for SQLite
Post Reply
tomr
Posts: 2
Joined: Wed 18 Jul 2012 19:10

Sqlite Caching problem

Post by tomr » Wed 18 Jul 2012 19:30

I am using devart dotConnect (latest build) in an asp.net(4.0) application using IIS7 to connect to a Sqlite (spiceworks) database located on a fileshare. This application only reads from the database.

My problem is that when updates to the database are made from a different application, and I select that data from my asp.net page, those recent changes are not returned. The old data is being cached somewhere but i cannot find where or how to disable it. I can always get the recent updates to be returned to my select queries by stopping and restarting my Application Pool in IIS.

I suspect it may be the WAL journal mode. I tried adding 'Journal Mode=WAL' to my connection string but it did not help.

Here is my connection string:
Data Source=\\myfileshare\SpiceworksDB\spiceworks.db;version=3;Read Uncommitted=true;

Any help on this would be greatly appreciated.

tomr
Posts: 2
Joined: Wed 18 Jul 2012 19:10

Re: Sqlite Caching problem

Post by tomr » Fri 20 Jul 2012 14:38

Here is an update on this problem. It has nothing to do with Devart, Sqlite or asp.net.

This is a SpiceWorks problem (feature). The Spiceworks product uses sqlite. According to them:

"Spiceworks locks the database in v5.1+. You need to stop Spiceworks, copy the database to a new location, restart spiceworks and then use that file for all of your secondary reporting tools.

Spiceworks does not support any application reading the database in a live fashion and it's one of the best ways you can go about screwing up your installation."

Post Reply