Concurrent database access in SQL 2005 Mobile
- From: sardo007 <sardo007@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Jul 2008 11:14:01 -0700
Hello all... I'm having a very annoying issue that's about to make me crazy.
I have a database application developed with VS2005 and OLEDB access to a
SQL 2005 Mobile database. While the application is running the same database
can be accessed by another notifying application that shoud add, modify or
delete rows in some tables. The problem is as follows:
1- If the main application creates, uses and then destroys the OLEDB
connections, everything works just fine: changes made by the notifying app.
are seen by the application. This just works too slowly for the customer in
some devices.
2- One workaroud for the previous problem I found in these forums is to
create a "dummy" connection and keep it open. That way the database file is
maintained in memory and every subsequent connection is created and opened
faster. This works fine except that any changes made by the notifying
application is not seen by the main application until the user exits and then
enters again.
3- I have recently discovered another problem: if the notifying program
deletes one row in a table, and the user tries to modify the contents of that
row (since he stills sees it, because the changes are invisible to him) the
database gets corrupted and it can't be accessed anymore from neither
application. Reads to the "nonexistent" data are OK, but they just should not
be there.
I've tried to change everything from transaction isolation method to rowset
properties regarding to the data visibility and the like... nothing works
except the "true" reset of the database file (closing all connections and
opening them again when you need them)
Is there a known issue, patch or anything I have to do explicitly to solve
this problem?
Any ideas will be welcome.
Thanx
.
- Follow-Ups:
- RE: Concurrent database access in SQL 2005 Mobile
- From: sardo007
- Re: Concurrent database access in SQL 2005 Mobile
- From: Ginny Caughey MVP
- RE: Concurrent database access in SQL 2005 Mobile
- Prev by Date: Re: error while editing a table schema
- Next by Date: Re: Concurrent database access in SQL 2005 Mobile
- Previous by thread: Re: error while editing a table schema
- Next by thread: Re: Concurrent database access in SQL 2005 Mobile
- Index(es):
Relevant Pages
|