Re: MATREADU/MATWRITE statements timing out

<big snip>>
Peter,

General rules are :

Pessimistic locks for transactions (required for transaction
boundaries anyway)
Optimistic locks for "masterfile updates" (which 'deteriorate' to
field by field comparisons during actual update, when a Pessimitic
locks is exterted whilst the actual update/comparison is done)
Hi Ross
Thanks for the response
Are you confirming that the user returns an original unaltered copy and an
altered copy?
That a comparison of original to file copy then takes place and the update
only continues if all is equal.
All updates are done on a field by field comparison.
Seems like there must be better ways to me. One way I have considered is to
issue an update token and only continue if it has not expired for this
record ie a new one has not been issued for the same record.
Regards
Peter McMurray

Whilst on comparisons, the 3rd alternative is that whilst your OLD
record # CURRENT record, your NEW field may = CURRENT field, in which
case all is AOK for 'update' (which doesn't need to take place for
that field)

In Visage we have an option for a manual resolution process that
displays all 3 values, but to date I'm not aware of anyone in the REAL
WORLD ever having seen it (how likely is it that multiple people would
change the same master file information to DIFFERENT values ... and if
they do, then we HAVE to defer to a person to resolve, 'cause there
are just tooooo many variables and not a fact to be found to guide us)

Multi-valued field (for notes) will typically either need some serious
work to identify changes OR may be reworked so that notes are treated
as unique "transactions"

HTH

(Did have a nice BIG response, but accidentally hit "discard" --> that
will teach me to formulate in word first)


.

Relevant Pages

  • Re: Sql Server Locks
    ... Tran and Commit Tran are as close together as possible and the transactions ... > The problem is with SQL Server Database Locks. ... > client A and reinserts the same with some data changes ... > provide us any good links for this kind of scenarios. ...
    (microsoft.public.sqlserver.clients)
  • Re: Transaction and locks
    ... You should read a bit more about transactions in Books OnLine. ... All transactions use locks, even in read uncommitted level you get exclusive ... all updates are automatically transactions. ... committed snapshot, snapshot) are optimistic. ...
    (microsoft.public.sqlserver.clients)
  • Re: can you tell me why this causes a deadlock?
    ... you need to ensure you obtain all the locks required for the whole ... Session 1: ... insert into joe with values ... what two locks my original two transactions got in reverse ...
    (comp.databases.ms-sqlserver)
  • Re: SqlDataReader default locking?
    ... Let's imagine we perform the 4 following transactions one after the other ... > sub-second response time where locks are held for the minimum amount ... > hold or honor any locks, and can give you dirty reads. ... >>I just wanted to know wheter any row locking takes place when we are ...
    (microsoft.public.dotnet.framework.adonet)