 | |
Issue with data migration from Sql 6.5 to Sql 2000 using bcp
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Issue with data migration from Sql 6.5 to Sql 2000 using bcp -
06-18-2008
, 09:08 PM
#2
| |||
| |||
|
|
Hi, My apologies if this question is not suitable to be posted here.. We are facing an issue while moving a Sql 6.5 database to a Sql 2000 server using bcp out/bcp in. We have moved several databases from Sql 6.5 to Sql 2000 earlier by scripting out and then bulk copying data using bcp, but now having issues with this database, specifically with one table. The table in qiestion has a combined primary key constituting four columns out of which two columns are of datetime datatype. I performed the following steps for copying the table data to target Sql 2000 db: 1 - recreated the table in target Sql 2000 db with script from source Sql 6.5 db (without creating the primary key) 2 - pulled data from source Sql 6.5 db using bcp out, and then inserted the data to target Sql 2000 table using bcp in. 3 - tried to recreate the primary key on the target table. This is when I get the following error: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '549994615'. Server: Msg 1750, Level 16, State 1, Line 3 Could not create constraint. See previous errors. The statement has been terminated. The primary key is existing in the source Sql 6.5 database. I checked that there are several duplicate values in the target table for this combined primary key. With bcp out, the datetime data in the bcp output file are of the format for example 'Nov 18 2005 12:00AM', and while I query the data in the db, it shows in the format '2005-11-18 00:00:00.000'. So in the source Sql 6.5 database(primary key exists here!!) as well the target Sql 2000 db(pk creation gives error), I see the same set of duplicate data for the primary key columns with datetime in the format '2005-11-18 00:00:00.000'. My confusion is - if these data values are duplicate, how can the primary key exist in the source 6.5 database ?? Or, am I missing to copy the datetime data properly from Sql 6.5 to Sql 2000 with bcp out/in ?? Is there any other option for me..? Please let me know if I could not explain this properly, or if some sample data is needed for my explaination. Thanks in advance for your guidance ..!! Regards, Himansu |
rows with identical primary key?
Can you please tell us the data type of the 4 columns of the combined
PK?
Have you also tried changing the date datatype before importing into
sql2000? If it's a date problem i would suggest to convert it to
varchar in the form: yyyymmdd with convert(varchar, yourcolumn, 112)
Last but not least: have you tried an internet search?
Bye,
M.
#3
| |||
| |||
|
|
Hi, My apologies if this question is not suitable to be posted here.. We are facing an issue while moving a Sql 6.5 database to a Sql 2000 server using bcp out/bcp in. We have moved several databases from Sql 6.5 to Sql 2000 earlier by scripting out and then bulk copying data using bcp, but now having issues with this database, specifically with one table. The table in qiestion has a combined primary key constituting four columns out of which two columns are of datetime datatype. I performed the following steps for copying the table data to target Sql 2000 db: 1 - recreated the table in target Sql 2000 db with script from source Sql 6.5 db (without creating the primary key) 2 - pulled data from source Sql 6.5 db using bcp out, and then inserted the data to target Sql 2000 table using bcp in. 3 - tried to recreate the primary key on the target table. This is when I get the following error: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '549994615'. Server: Msg 1750, Level 16, State 1, Line 3 Could not create constraint. See previous errors. The statement has been terminated. The primary key is existing in the source Sql 6.5 database. I checked that there are several duplicate values in the target table for this combined primary key. With bcp out, the datetime data in the bcp output file are of the format for example 'Nov 18 2005 12:00AM', and while I query the data in the db, it shows in the format '2005-11-18 00:00:00.000'. So in the source Sql 6.5 database(primary key exists here!!) as well the target Sql 2000 db(pk creation gives error), I see the same set of duplicate data for the primary key columns with datetime in the format '2005-11-18 00:00:00.000'. My confusion is - if these data values are duplicate, how can the primary key exist in the source 6.5 database ?? Or, am I missing to copy the datetime data properly from Sql 6.5 to Sql 2000 with bcp out/in ?? Is there any other option for me..? Please let me know if I could not explain this properly, or if some sample data is needed for my explaination. Thanks in advance for your guidance ..!! Regards, Himansu |
rows with identical primary key?
Can you please tell us the data type of the 4 columns of the combined
PK?
Have you also tried changing the date datatype before importing into
sql2000? If it's a date problem i would suggest to convert it to
varchar in the form: yyyymmdd with convert(varchar, yourcolumn, 112)
Last but not least: have you tried an internet search?
Bye,
M.
#4
| |||
| |||
|
|
Hi, My apologies if this question is not suitable to be posted here.. We are facing an issue while moving a Sql 6.5 database to a Sql 2000 server using bcp out/bcp in. We have moved several databases from Sql 6.5 to Sql 2000 earlier by scripting out and then bulk copying data using bcp, but now having issues with this database, specifically with one table. The table in qiestion has a combined primary key constituting four columns out of which two columns are of datetime datatype. I performed the following steps for copying the table data to target Sql 2000 db: 1 - recreated the table in target Sql 2000 db with script from source Sql 6.5 db (without creating the primary key) 2 - pulled data from source Sql 6.5 db using bcp out, and then inserted the data to target Sql 2000 table using bcp in. 3 - tried to recreate the primary key on the target table. This is when I get the following error: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '549994615'. Server: Msg 1750, Level 16, State 1, Line 3 Could not create constraint. See previous errors. The statement has been terminated. The primary key is existing in the source Sql 6.5 database. I checked that there are several duplicate values in the target table for this combined primary key. With bcp out, the datetime data in the bcp output file are of the format for example 'Nov 18 2005 12:00AM', and while I query the data in the db, it shows in the format '2005-11-18 00:00:00.000'. So in the source Sql 6.5 database(primary key exists here!!) as well the target Sql 2000 db(pk creation gives error), I see the same set of duplicate data for the primary key columns with datetime in the format '2005-11-18 00:00:00.000'. My confusion is - if these data values are duplicate, how can the primary key exist in the source 6.5 database ?? Or, am I missing to copy the datetime data properly from Sql 6.5 to Sql 2000 with bcp out/in ?? Is there any other option for me..? Please let me know if I could not explain this properly, or if some sample data is needed for my explaination. Thanks in advance for your guidance ..!! Regards, Himansu |
rows with identical primary key?
Can you please tell us the data type of the 4 columns of the combined
PK?
Have you also tried changing the date datatype before importing into
sql2000? If it's a date problem i would suggest to convert it to
varchar in the form: yyyymmdd with convert(varchar, yourcolumn, 112)
Last but not least: have you tried an internet search?
Bye,
M.
#5
| |||
| |||
|
|
Hi, My apologies if this question is not suitable to be posted here.. We are facing an issue while moving a Sql 6.5 database to a Sql 2000 server using bcp out/bcp in. We have moved several databases from Sql 6.5 to Sql 2000 earlier by scripting out and then bulk copying data using bcp, but now having issues with this database, specifically with one table. The table in qiestion has a combined primary key constituting four columns out of which two columns are of datetime datatype. I performed the following steps for copying the table data to target Sql 2000 db: 1 - recreated the table in target Sql 2000 db with script from source Sql 6.5 db (without creating the primary key) 2 - pulled data from source Sql 6.5 db using bcp out, and then inserted the data to target Sql 2000 table using bcp in. 3 - tried to recreate the primary key on the target table. This is when I get the following error: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '549994615'. Server: Msg 1750, Level 16, State 1, Line 3 Could not create constraint. See previous errors. The statement has been terminated. The primary key is existing in the source Sql 6.5 database. I checked that there are several duplicate values in the target table for this combined primary key. With bcp out, the datetime data in the bcp output file are of the format for example 'Nov 18 2005 12:00AM', and while I query the data in the db, it shows in the format '2005-11-18 00:00:00.000'. So in the source Sql 6.5 database(primary key exists here!!) as well the target Sql 2000 db(pk creation gives error), I see the same set of duplicate data for the primary key columns with datetime in the format '2005-11-18 00:00:00.000'. My confusion is - if these data values are duplicate, how can the primary key exist in the source 6.5 database ?? Or, am I missing to copy the datetime data properly from Sql 6.5 to Sql 2000 with bcp out/in ?? Is there any other option for me..? Please let me know if I could not explain this properly, or if some sample data is needed for my explaination. Thanks in advance for your guidance ..!! Regards, Himansu |
rows with identical primary key?
Can you please tell us the data type of the 4 columns of the combined
PK?
Have you also tried changing the date datatype before importing into
sql2000? If it's a date problem i would suggest to convert it to
varchar in the form: yyyymmdd with convert(varchar, yourcolumn, 112)
Last but not least: have you tried an internet search?
Bye,
M.
#6
| |||
| |||
|
|
Hi, My apologies if this question is not suitable to be posted here.. We are facing an issue while moving a Sql 6.5 database to a Sql 2000 server using bcp out/bcp in. We have moved several databases from Sql 6.5 to Sql 2000 earlier by scripting out and then bulk copying data using bcp, but now having issues with this database, specifically with one table. The table in qiestion has a combined primary key constituting four columns out of which two columns are of datetime datatype. I performed the following steps for copying the table data to target Sql 2000 db: 1 - recreated the table in target Sql 2000 db with script from source Sql 6.5 db (without creating the primary key) 2 - pulled data from source Sql 6.5 db using bcp out, and then inserted the data to target Sql 2000 table using bcp in. 3 - tried to recreate the primary key on the target table. This is when I get the following error: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '549994615'. Server: Msg 1750, Level 16, State 1, Line 3 Could not create constraint. See previous errors. The statement has been terminated. The primary key is existing in the source Sql 6.5 database. I checked that there are several duplicate values in the target table for this combined primary key. With bcp out, the datetime data in the bcp output file are of the format for example 'Nov 18 2005 12:00AM', and while I query the data in the db, it shows in the format '2005-11-18 00:00:00.000'. So in the source Sql 6.5 database(primary key exists here!!) as well the target Sql 2000 db(pk creation gives error), I see the same set of duplicate data for the primary key columns with datetime in the format '2005-11-18 00:00:00.000'. My confusion is - if these data values are duplicate, how can the primary key exist in the source 6.5 database ?? Or, am I missing to copy the datetime data properly from Sql 6.5 to Sql 2000 with bcp out/in ?? Is there any other option for me..? Please let me know if I could not explain this properly, or if some sample data is needed for my explaination. Thanks in advance for your guidance ..!! Regards, Himansu |
rows with identical primary key?
Can you please tell us the data type of the 4 columns of the combined
PK?
Have you also tried changing the date datatype before importing into
sql2000? If it's a date problem i would suggest to convert it to
varchar in the form: yyyymmdd with convert(varchar, yourcolumn, 112)
Last but not least: have you tried an internet search?
Bye,
M.
#7
| |||
| |||
|
|
Hi, My apologies if this question is not suitable to be posted here.. We are facing an issue while moving a Sql 6.5 database to a Sql 2000 server using bcp out/bcp in. We have moved several databases from Sql 6.5 to Sql 2000 earlier by scripting out and then bulk copying data using bcp, but now having issues with this database, specifically with one table. The table in qiestion has a combined primary key constituting four columns out of which two columns are of datetime datatype. I performed the following steps for copying the table data to target Sql 2000 db: 1 - recreated the table in target Sql 2000 db with script from source Sql 6.5 db (without creating the primary key) 2 - pulled data from source Sql 6.5 db using bcp out, and then inserted the data to target Sql 2000 table using bcp in. 3 - tried to recreate the primary key on the target table. This is when I get the following error: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '549994615'. Server: Msg 1750, Level 16, State 1, Line 3 Could not create constraint. See previous errors. The statement has been terminated. The primary key is existing in the source Sql 6.5 database. I checked that there are several duplicate values in the target table for this combined primary key. With bcp out, the datetime data in the bcp output file are of the format for example 'Nov 18 2005 12:00AM', and while I query the data in the db, it shows in the format '2005-11-18 00:00:00.000'. So in the source Sql 6.5 database(primary key exists here!!) as well the target Sql 2000 db(pk creation gives error), I see the same set of duplicate data for the primary key columns with datetime in the format '2005-11-18 00:00:00.000'. My confusion is - if these data values are duplicate, how can the primary key exist in the source 6.5 database ?? Or, am I missing to copy the datetime data properly from Sql 6.5 to Sql 2000 with bcp out/in ?? Is there any other option for me..? Please let me know if I could not explain this properly, or if some sample data is needed for my explaination. Thanks in advance for your guidance ..!! Regards, Himansu |
rows with identical primary key?
Can you please tell us the data type of the 4 columns of the combined
PK?
Have you also tried changing the date datatype before importing into
sql2000? If it's a date problem i would suggest to convert it to
varchar in the form: yyyymmdd with convert(varchar, yourcolumn, 112)
Last but not least: have you tried an internet search?
Bye,
M.
#8
| |||
| |||
|
|
Hi, My apologies if this question is not suitable to be posted here.. We are facing an issue while moving a Sql 6.5 database to a Sql 2000 server using bcp out/bcp in. We have moved several databases from Sql 6.5 to Sql 2000 earlier by scripting out and then bulk copying data using bcp, but now having issues with this database, specifically with one table. The table in qiestion has a combined primary key constituting four columns out of which two columns are of datetime datatype. I performed the following steps for copying the table data to target Sql 2000 db: 1 - recreated the table in target Sql 2000 db with script from source Sql 6.5 db (without creating the primary key) 2 - pulled data from source Sql 6.5 db using bcp out, and then inserted the data to target Sql 2000 table using bcp in. 3 - tried to recreate the primary key on the target table. This is when I get the following error: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '549994615'. Server: Msg 1750, Level 16, State 1, Line 3 Could not create constraint. See previous errors. The statement has been terminated. The primary key is existing in the source Sql 6.5 database. I checked that there are several duplicate values in the target table for this combined primary key. With bcp out, the datetime data in the bcp output file are of the format for example 'Nov 18 2005 12:00AM', and while I query the data in the db, it shows in the format '2005-11-18 00:00:00.000'. So in the source Sql 6.5 database(primary key exists here!!) as well the target Sql 2000 db(pk creation gives error), I see the same set of duplicate data for the primary key columns with datetime in the format '2005-11-18 00:00:00.000'. My confusion is - if these data values are duplicate, how can the primary key exist in the source 6.5 database ?? Or, am I missing to copy the datetime data properly from Sql 6.5 to Sql 2000 with bcp out/in ?? Is there any other option for me..? Please let me know if I could not explain this properly, or if some sample data is needed for my explaination. Thanks in advance for your guidance ..!! Regards, Himansu |
rows with identical primary key?
Can you please tell us the data type of the 4 columns of the combined
PK?
Have you also tried changing the date datatype before importing into
sql2000? If it's a date problem i would suggest to convert it to
varchar in the form: yyyymmdd with convert(varchar, yourcolumn, 112)
Last but not least: have you tried an internet search?
Bye,
M.
#9
| |||
| |||
|
|
Hi, My apologies if this question is not suitable to be posted here.. We are facing an issue while moving a Sql 6.5 database to a Sql 2000 server using bcp out/bcp in. We have moved several databases from Sql 6.5 to Sql 2000 earlier by scripting out and then bulk copying data using bcp, but now having issues with this database, specifically with one table. The table in qiestion has a combined primary key constituting four columns out of which two columns are of datetime datatype. I performed the following steps for copying the table data to target Sql 2000 db: 1 - recreated the table in target Sql 2000 db with script from source Sql 6.5 db (without creating the primary key) 2 - pulled data from source Sql 6.5 db using bcp out, and then inserted the data to target Sql 2000 table using bcp in. 3 - tried to recreate the primary key on the target table. This is when I get the following error: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '549994615'. Server: Msg 1750, Level 16, State 1, Line 3 Could not create constraint. See previous errors. The statement has been terminated. The primary key is existing in the source Sql 6.5 database. I checked that there are several duplicate values in the target table for this combined primary key. With bcp out, the datetime data in the bcp output file are of the format for example 'Nov 18 2005 12:00AM', and while I query the data in the db, it shows in the format '2005-11-18 00:00:00.000'. So in the source Sql 6.5 database(primary key exists here!!) as well the target Sql 2000 db(pk creation gives error), I see the same set of duplicate data for the primary key columns with datetime in the format '2005-11-18 00:00:00.000'. My confusion is - if these data values are duplicate, how can the primary key exist in the source 6.5 database ?? Or, am I missing to copy the datetime data properly from Sql 6.5 to Sql 2000 with bcp out/in ?? Is there any other option for me..? Please let me know if I could not explain this properly, or if some sample data is needed for my explaination. Thanks in advance for your guidance ..!! Regards, Himansu |
rows with identical primary key?
Can you please tell us the data type of the 4 columns of the combined
PK?
Have you also tried changing the date datatype before importing into
sql2000? If it's a date problem i would suggest to convert it to
varchar in the form: yyyymmdd with convert(varchar, yourcolumn, 112)
Last but not least: have you tried an internet search?
Bye,
M.
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.