Methods for moving serial-keyed data from one serv

Posted in 2008

Knox, Ernest — Wed, 23 Jan 2008 19:05:04 — source: IIUG Forums & Mailing Lists

Is there or does anyone have a proven method(s) to moving serial-keyed data from one database server to another, without losing the values? Thanks, ************************************** Ernie Knox Sears Holding Co. IT Database Administrator Specialist IT Service Management, Strategy & Architecture 3333 Beverly Rd., B4-266A Hoffman Estates, IL. 60179 Office: (847) 286-5735 Fax: (847) 645-3874 Pager: (800) 759-8352 Pin#: 7271042 Email: eknox@sears.com " It's always a great day to watch Football ! " **************************************

↪ replying to Knox, Ernest

Jarrod Teale — Wed, 23 Jan 2008 19:35:08 — source: IIUG Forums & Mailing Lists

If the target database is empty, then a straight unload / load or direct insert will bring the value across as it stands. Dbexport / dbimport will also preserve the values. I have a more complicated set up with multiple source databases sending data into a single central one. To preserve the serial values, I am using Enterprise Replication and the CDR Serial values - which ensure the serial keys generated on each server are unique, so can safely be combined into a single table. I think some more information around what you are trying to do would be helpful. Jarrod Teale -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Knox, Ernest Sent: Thursday, 24 January 2008 8:05 a.m. To: ids@iiug.org Subject: Methods for moving serial-keyed data from one .... [11076] Is there or does anyone have a proven method(s) to moving serial-keyed data from one database server to another, without losing the values? Thanks, ************************************** Ernie Knox Sears Holding Co. IT Database Administrator Specialist IT Service Management, Strategy & Architecture 3333 Beverly Rd., B4-266A Hoffman Estates, IL. 60179 Office: (847) 286-5735 Fax: (847) 645-3874 Pager: (800) 759-8352 Pin#: 7271042 Email: eknox@sears.com " It's always a great day to watch Football ! " ************************************** ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum. See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!! DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/

↪ replying to Jarrod Teale

Art S. Kagel — Wed, 23 Jan 2008 20:03:25 — source: IIUG Forums & Mailing Lists

Jarrod Teale wrote: As Jarrod points out, if the target database is empty, no problems with the copy at all. If there are existing rows in the target tables which may clash on the serial column with the rows being copied, then you'll have to write a custom copy/import tool to acquire a new serial value for the master record and insert any dependent records into the child tables with that new value in the dependent column instead of the original serial value. I've done a few of those myself. Art S. Kagel Oninit > If the target database is empty, then a straight unload / load or direct > insert will bring the value across as it stands. > Dbexport / dbimport will also preserve the values. > > I have a more complicated set up with multiple source databases sending > data into a single central one. To preserve the serial values, I am > using Enterprise Replication and the CDR Serial values - which ensure > the serial keys generated on each server are unique, so can safely be > combined into a single table. > > I think some more information around what you are trying to do would be > helpful. > > Jarrod Teale > > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Knox, Ernest > Sent: Thursday, 24 January 2008 8:05 a.m. > To: ids@iiug.org > Subject: Methods for moving serial-keyed data from one .... [11076] > > Is there or does anyone have a proven method(s) to moving serial-keyed > data from one database server to another, without losing the values? > > Thanks, > > ************************************** > Ernie Knox > Sears Holding Co. > IT Database Administrator Specialist > > > ================================================================================ =========== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.oninit.com/home/disclaimer.php ================================================================================ ===========

↪ replying to Art S. Kagel

Knox, Ernest — Wed, 23 Jan 2008 21:46:20 — source: IIUG Forums & Mailing Lists

Thanks for those that replied. The method(s) worked. Thanks, ************************************** Ernie Knox Sears Holding Co. IT Database Administrator Specialist IT Service Management, Strategy & Architecture 3333 Beverly Rd., B4-266A Hoffman Estates, IL. 60179 Office: (847) 286-5735 Fax: (847) 645-3874 Pager: (800) 759-8352 Pin#: 7271042 Email: eknox@sears.com " It's always a great day to watch Football ! " ************************************** -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art S. Kagel (Oninit LLC) Sent: Wednesday, January 23, 2008 2:03 PM To: ids@iiug.org Subject: Re: Methods for moving serial-keyed data from .... [11078] Jarrod Teale wrote: As Jarrod points out, if the target database is empty, no problems with the copy at all. If there are existing rows in the target tables which may clash on the serial column with the rows being copied, then you'll have to write a custom copy/import tool to acquire a new serial value for the master record and insert any dependent records into the child tables with that new value in the dependent column instead of the original serial value. I've done a few of those myself. Art S. Kagel Oninit > If the target database is empty, then a straight unload / load or direct > insert will bring the value across as it stands. > Dbexport / dbimport will also preserve the values. > > I have a more complicated set up with multiple source databases sending > data into a single central one. To preserve the serial values, I am > using Enterprise Replication and the CDR Serial values - which ensure > the serial keys generated on each server are unique, so can safely be > combined into a single table. > > I think some more information around what you are trying to do would be > helpful. > > Jarrod Teale > > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Knox, Ernest > Sent: Thursday, 24 January 2008 8:05 a.m. > To: ids@iiug.org > Subject: Methods for moving serial-keyed data from one .... [11076] > > Is there or does anyone have a proven method(s) to moving serial-keyed > data from one database server to another, without losing the values? > > Thanks, > > ************************************** > Ernie Knox > Sears Holding Co. > IT Database Administrator Specialist > > > ================================================================================ =========== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.oninit.com/home/disclaimer.php ================================================================================ =========== ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!!