 | |
Issue with date move from Sql 6.5 to Sql 2000 using bcp
microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools
 |
| | Thread Tools | Display Modes |
#21
 
| |||
| |||
|
Re: Issue with date move from Sql 6.5 to Sql 2000 using bcp -
06-20-2008
, 05:38 PM
|
The table does not have any sysname datatype. I tried BCP from sql 6.5 to Sql 2000 with the native mode as you suggested, but got the following error: Starting copy... SQLState = 22001, NativeError = 0 Error = [Microsoft][ODBC SQL Server Driver]String data, right truncation SQLState = 22001, NativeError = 0 I checked that both the source and target tables have the same columns, datatypes and lengths. Not sure here about the error. |
but I remember that we used native format, because we were hit by that
sysname thing I mentioned. So I don't really know what this may be due
to.
Ah, I know! It's a collation issue! We have had similar errors when we
bulk-copied between SQL 2005 machines with different collations.
In any case, I think you need to move to plan B:
Quote:
|
You suggested the second alternative for BCP 2000 to get the data from SQL 6.5.. Would you please elaborate how this can be achieved.. |
can try character format, or you can try native format. If you use
native format, use the format option of BCP to create a format file.
The format file will include a collation name, which should deal with
any collation issues.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#22
| |||
| |||
|
|
The table does not have any sysname datatype. I tried BCP from sql 6.5 to Sql 2000 with the native mode as you suggested, but got the following error: Starting copy... SQLState = 22001, NativeError = 0 Error = [Microsoft][ODBC SQL Server Driver]String data, right truncation SQLState = 22001, NativeError = 0 I checked that both the source and target tables have the same columns, datatypes and lengths. Not sure here about the error. |
but I remember that we used native format, because we were hit by that
sysname thing I mentioned. So I don't really know what this may be due
to.
Ah, I know! It's a collation issue! We have had similar errors when we
bulk-copied between SQL 2005 machines with different collations.
In any case, I think you need to move to plan B:
Quote:
|
You suggested the second alternative for BCP 2000 to get the data from SQL 6.5.. Would you please elaborate how this can be achieved.. |
can try character format, or you can try native format. If you use
native format, use the format option of BCP to create a format file.
The format file will include a collation name, which should deal with
any collation issues.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#23
| |||
| |||
|
|
The table does not have any sysname datatype. I tried BCP from sql 6.5 to Sql 2000 with the native mode as you suggested, but got the following error: Starting copy... SQLState = 22001, NativeError = 0 Error = [Microsoft][ODBC SQL Server Driver]String data, right truncation SQLState = 22001, NativeError = 0 I checked that both the source and target tables have the same columns, datatypes and lengths. Not sure here about the error. |
but I remember that we used native format, because we were hit by that
sysname thing I mentioned. So I don't really know what this may be due
to.
Ah, I know! It's a collation issue! We have had similar errors when we
bulk-copied between SQL 2005 machines with different collations.
In any case, I think you need to move to plan B:
Quote:
|
You suggested the second alternative for BCP 2000 to get the data from SQL 6.5.. Would you please elaborate how this can be achieved.. |
can try character format, or you can try native format. If you use
native format, use the format option of BCP to create a format file.
The format file will include a collation name, which should deal with
any collation issues.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#24
| |||
| |||
|
|
The table does not have any sysname datatype. I tried BCP from sql 6.5 to Sql 2000 with the native mode as you suggested, but got the following error: Starting copy... SQLState = 22001, NativeError = 0 Error = [Microsoft][ODBC SQL Server Driver]String data, right truncation SQLState = 22001, NativeError = 0 I checked that both the source and target tables have the same columns, datatypes and lengths. Not sure here about the error. |
but I remember that we used native format, because we were hit by that
sysname thing I mentioned. So I don't really know what this may be due
to.
Ah, I know! It's a collation issue! We have had similar errors when we
bulk-copied between SQL 2005 machines with different collations.
In any case, I think you need to move to plan B:
Quote:
|
You suggested the second alternative for BCP 2000 to get the data from SQL 6.5.. Would you please elaborate how this can be achieved.. |
can try character format, or you can try native format. If you use
native format, use the format option of BCP to create a format file.
The format file will include a collation name, which should deal with
any collation issues.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#25
| |||
| |||
|
|
The table does not have any sysname datatype. I tried BCP from sql 6.5 to Sql 2000 with the native mode as you suggested, but got the following error: Starting copy... SQLState = 22001, NativeError = 0 Error = [Microsoft][ODBC SQL Server Driver]String data, right truncation SQLState = 22001, NativeError = 0 I checked that both the source and target tables have the same columns, datatypes and lengths. Not sure here about the error. |
but I remember that we used native format, because we were hit by that
sysname thing I mentioned. So I don't really know what this may be due
to.
Ah, I know! It's a collation issue! We have had similar errors when we
bulk-copied between SQL 2005 machines with different collations.
In any case, I think you need to move to plan B:
Quote:
|
You suggested the second alternative for BCP 2000 to get the data from SQL 6.5.. Would you please elaborate how this can be achieved.. |
can try character format, or you can try native format. If you use
native format, use the format option of BCP to create a format file.
The format file will include a collation name, which should deal with
any collation issues.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#26
| |||
| |||
|
|
The table does not have any sysname datatype. I tried BCP from sql 6.5 to Sql 2000 with the native mode as you suggested, but got the following error: Starting copy... SQLState = 22001, NativeError = 0 Error = [Microsoft][ODBC SQL Server Driver]String data, right truncation SQLState = 22001, NativeError = 0 I checked that both the source and target tables have the same columns, datatypes and lengths. Not sure here about the error. |
but I remember that we used native format, because we were hit by that
sysname thing I mentioned. So I don't really know what this may be due
to.
Ah, I know! It's a collation issue! We have had similar errors when we
bulk-copied between SQL 2005 machines with different collations.
In any case, I think you need to move to plan B:
Quote:
|
You suggested the second alternative for BCP 2000 to get the data from SQL 6.5.. Would you please elaborate how this can be achieved.. |
can try character format, or you can try native format. If you use
native format, use the format option of BCP to create a format file.
The format file will include a collation name, which should deal with
any collation issues.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#27
| |||
| |||
|
|
The table does not have any sysname datatype. I tried BCP from sql 6.5 to Sql 2000 with the native mode as you suggested, but got the following error: Starting copy... SQLState = 22001, NativeError = 0 Error = [Microsoft][ODBC SQL Server Driver]String data, right truncation SQLState = 22001, NativeError = 0 I checked that both the source and target tables have the same columns, datatypes and lengths. Not sure here about the error. |
but I remember that we used native format, because we were hit by that
sysname thing I mentioned. So I don't really know what this may be due
to.
Ah, I know! It's a collation issue! We have had similar errors when we
bulk-copied between SQL 2005 machines with different collations.
In any case, I think you need to move to plan B:
Quote:
|
You suggested the second alternative for BCP 2000 to get the data from SQL 6.5.. Would you please elaborate how this can be achieved.. |
can try character format, or you can try native format. If you use
native format, use the format option of BCP to create a format file.
The format file will include a collation name, which should deal with
any collation issues.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#28
| |||
| |||
|
|
The table does not have any sysname datatype. I tried BCP from sql 6.5 to Sql 2000 with the native mode as you suggested, but got the following error: Starting copy... SQLState = 22001, NativeError = 0 Error = [Microsoft][ODBC SQL Server Driver]String data, right truncation SQLState = 22001, NativeError = 0 I checked that both the source and target tables have the same columns, datatypes and lengths. Not sure here about the error. |
but I remember that we used native format, because we were hit by that
sysname thing I mentioned. So I don't really know what this may be due
to.
Ah, I know! It's a collation issue! We have had similar errors when we
bulk-copied between SQL 2005 machines with different collations.
In any case, I think you need to move to plan B:
Quote:
|
You suggested the second alternative for BCP 2000 to get the data from SQL 6.5.. Would you please elaborate how this can be achieved.. |
can try character format, or you can try native format. If you use
native format, use the format option of BCP to create a format file.
The format file will include a collation name, which should deal with
any collation issues.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
|
« 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.