Row level tracking

[Michael S. Montoya]

I have a database that has around 50 tables. I notice that somehow Row Level
tracking is turned on with some of the tables, but not all. Is Row Level
recommended? Does it slow down a database resulting in slower form
loads/queries, etc??

Thanks in advance

Michael

 

[Jamie Richards]

As there is no answer to this yet, I'll offer my 2 cents worth.

I believe tracking only really becomes important in a multi-user
environment, in particualr when using replicated databases. If you have row
level tracking on for a table it means that only one user can edit any
field in that record at any given time. If another user attempts to edit a
record with row level tracking on, a conflict will occur. To reduce
conflicts in these environments, provided it suits the way your application
is desgined to work, you can opt not to use row level tracking. This means
that two users *can* edit the same record concurrently, but *not* the same
field in a record (as the conflict tracking will apply to columns instead of
rows).

Did that make any sense?


Jamie