Databases and other data stores which treat the integrity of data as paramount often include the ability to handle transactions to maintain the integrity of data. A single transaction consists of one or more independent units of work, each reading and/or writing information to a database or other data store.
I use the following code (which is a simplified version of what happen on a server) :
tstartfor1Test.Test is a persistent class that inherit from %Persistent :
I think delocks are needed because of the transaction, to maintain data consistency, but why exactly are they needed here ?
Is there some options that can be used to avoid the delocks ? (even if data consistency is lost).
Hi,
The system I am working on processes large numbers of records. Inserts, updates and so forth. There are multiple processes that can potentially work on the same table at the same time.
It is an almost impossible task to try and time these processes to not run at the same time, due to volumes, SLAs, etc.
Every now and then there are a few locking issues, Not many considering the volumes. It is just a bit of a nuisance as we need to reprocess these records later.
All the selects on the processes run at IsolationMode 0 and the transactions are kept as short as possible.
Hi, I'm wondering what are the diferences between a method or classmethod with the language set at tsql and a querry writen in sql.
If anyone know if there is some difference and what they are, I would be glad to learn. 😊