Re: SQL Exclusive Locks -- MIDRANGE-L

Subject: Re: SQL Exclusive Locks
From: dlclark@xxxxxxxxxxxxxxxx
Date: Fri, 9 Feb 2018 15:10:06 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/09/2018
02:40:57 PM:

We are at 7.2. I have a table with an identity key which is
generated always, a foreign key constraint, and a row change timestamp
with is generated always. Why does SQL require an exclusive lock on the

foreign table when I'm trying to alter the identity key to generated by
default? Aaarrrggghhh!!!

I found my workaround. I don't ALTER the table but I specify
Overriding System Value on the INSERT to keep the identity and row change
timestamps as they were.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.