DTS Truncates data to destination

Hi all
I am using SQL Server 2000, since I dont have OLEDB provider for
Postgres, and SSIS does not support ODBC connection for migartion of
data.
I want to move data from my source tables to other database, for about
1000 tables.
Problem is that size of columns in source is large while the size of
columns in destination is small. I dont have control over desing of
destination database.
When I migrate data from source to destination, DTS truncate data to
size of dstination column and migarate data, but does not show any
warning that data is truncated.
If I will get warning it will be definately good for us to find out
tables in which data is truncated.
Because this we are not able to find out for which columns data is
truncated, its a big headache for the developers.
RegardsHi
http://pgfoundry.org/projects/oledb seems to be the project that is building
an OLEDB driver for progress! You may want to try using an interim file
format exported using SSIS (say Excel) or possibly use a linked server
instead.
John
"shahdharti@.gmail.com" wrote:

> Hi all
> I am using SQL Server 2000, since I dont have OLEDB provider for
> Postgres, and SSIS does not support ODBC connection for migartion of
> data.
> I want to move data from my source tables to other database, for about
> 1000 tables.
> Problem is that size of columns in source is large while the size of
> columns in destination is small. I dont have control over desing of
> destination database.
> When I migrate data from source to destination, DTS truncate data to
> size of dstination column and migarate data, but does not show any
> warning that data is truncated.
> If I will get warning it will be definately good for us to find out
> tables in which data is truncated.
> Because this we are not able to find out for which columns data is
> truncated, its a big headache for the developers.
>
> Regards
>|||Hi
http://pgfoundry.org/projects/oledb seems to be the project that is building
an OLEDB driver for progress! You may want to try using an interim file
format exported using SSIS (say Excel) or possibly use a linked server
instead.
John
"shahdharti@.gmail.com" wrote:

> Hi all
> I am using SQL Server 2000, since I dont have OLEDB provider for
> Postgres, and SSIS does not support ODBC connection for migartion of
> data.
> I want to move data from my source tables to other database, for about
> 1000 tables.
> Problem is that size of columns in source is large while the size of
> columns in destination is small. I dont have control over desing of
> destination database.
> When I migrate data from source to destination, DTS truncate data to
> size of dstination column and migarate data, but does not show any
> warning that data is truncated.
> If I will get warning it will be definately good for us to find out
> tables in which data is truncated.
> Because this we are not able to find out for which columns data is
> truncated, its a big headache for the developers.
>
> Regards
>