Can you update your post to ask specifically
a)if someone has encountered locks while strictly doing SELECT statements?
b)Does the "with (nolock)" work the same for UniVerse as it does for SQL
Server?
c)Do transaction isolation levels apply to users or transaction types, and
how can they be adjusted...
Thanks Pam. I think we're getting somewhere here.
Chris
-----Original Message-----
From: Pamela J Robbins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 28, 2007 10:27 AM
To: Chris Dunbar
Subject: [Fwd: Re: [U2] SQL query locks]
-------- Original Message --------
Subject: Re: [U2] SQL query locks
Date: Tue, 28 Aug 2007 16:58:04 +1000
From: Ray Wurlod <[EMAIL PROTECTED]>
Reply-To: u2-users@listserver.u2ug.org
To: u2-users@listserver.u2ug.org
If this is UniVerse there is a uvconfig parameter MAXRLOCK that specifies
how many record locks to take (on an INSERT, UPDATE or DELETE statement)
before choosing to use a FILELOCK. Reducing this parameter will mean fewer
record locks per query, at the cost of greater danger of another updating
process being locked out of the table till the first process finishes its
updates.
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
--
Pamela J Robbins New Bolton Center
Senior Programmer Analyst School of Veterinary Medicine
[EMAIL PROTECTED] University of Pennsylvania
610-925-6438
--
Pamela J Robbins New Bolton Center
Senior Programmer Analyst School of Veterinary Medicine
[EMAIL PROTECTED] University of Pennsylvania
610-925-6438
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
