|
Yeah, totally unacceptable. If that identity column is used as a primary
key, (like order number) and then there are dependencies off of that (like
order number in the order line table) you're not going to be happy.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Art
Tostaine, Jr.
Sent: Wednesday, October 14, 2020 11:50 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Data replication of Identity values
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
Thank you Charles. I agree they should know but say they've never dealt
with this before.
We are using HA right now to sync our production system to a production
system in the cloud. This morning, we cut off comms and we began testing
in the cloud. We tried to insert a record to a table with an identity
column. The rows in the table match but the identity value is from when
the cloud system was setup from our system save on 9/10.
Art
On Wed, Oct 14, 2020 at 11:15 AM Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
First off...I'd say you need a new HA vendor...had?
Secondly, not quite following what you mean by "SQL identity value isn't
updating"
Are the rows being inserted? Using the same value as the source table
--
Are you having a problem when the secondary system becomes primary?
You may have to include an ALTER TABLE ALTER COLUMN myid GENERATED ALWAYS
RESTART AT ...
As part of your switch over...
But again, your HA vendor should be experienced with identity columns at
this point.
Charles
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.