Identity column re-using existing numbers? -- MIDRANGE-L

Subject: Identity column re-using existing numbers?
From: Matt Olson <Matt.Olson@xxxxxxxx>
Date: Tue, 4 Dec 2018 19:17:42 +0000
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>

We migrated some of our tables to another partition for testing and we have noticed that their identity columns which should generate the next available number is infact generating an existing number and failing the primary key check. Has anyone see this before?

There some easy command to restart identity value to the next available number?

We are mystified why this didn't come over during the restore of that file...

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Identity column re-using existing numbers? , Arco Simonse
Re: Identity column re-using existing numbers? , Arco Simonse
Re: Identity column re-using existing numbers? , Evan Harris
RE: Identity column re-using existing numbers? , Matt Olson

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.