ETL library

We are looking for an ETL library or callable application that would
allow us to transfer and transform data between platforms but mainly
into a SQL server database. We would be calling this tool from
javascript programs. Is there something out there in the midrange
price-wise? So far I am finding just high-end ETL tools that are a
little over kill for us.

Thanks."elizabeth" <ezelasky@.hotmail.com> wrote in message
news:78393913.0409150439.818af56@.posting.google.co m...
> We are looking for an ETL library or callable application that would
> allow us to transfer and transform data between platforms but mainly
> into a SQL server database. We would be calling this tool from
> javascript programs. Is there something out there in the midrange
> price-wise? So far I am finding just high-end ETL tools that are a
> little over kill for us.
>
> Thanks.

Have you looked at DTS, which is included with MSSQL? It has a command-line
executable and a COM interface available. See "Data Transformation Services"
in Books Online for more details.

If DTS isn't suitable for you, you might want to be more specific about what
features you require.

Simon|||Folks here felt that DTS was slow (copied record by record) and buggy
that is why I was asked to search for something else. What we need is
fairly basic...to be able to move large amounts of data (in some
cases > 2 gigs) between a variety of sources (flat files, FoxPro &
Dbase) into a SQL Server database. We need to be able to set or
specify the table structure "on-the-fly" thus the reason for calling
it from a scripting environment or another environment.

Thanks.
> Have you looked at DTS, which is included with MSSQL? It has a command-line
> executable and a COM interface available. See "Data Transformation Services"
> in Books Online for more details.
> If DTS isn't suitable for you, you might want to be more specific about what
> features you require.
> Simon|||DTS can use 'fast load' bulk insert techniques to import data. This is the
fastest way to get data into SQL Server. You can create DTS packages 'on
the fly' programmatically and have control over the object model.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"elizabeth" <ezelasky@.hotmail.com> wrote in message
news:78393913.0409151028.7fcc0aca@.posting.google.c om...
> Folks here felt that DTS was slow (copied record by record) and buggy
> that is why I was asked to search for something else. What we need is
> fairly basic...to be able to move large amounts of data (in some
> cases > 2 gigs) between a variety of sources (flat files, FoxPro &
> Dbase) into a SQL Server database. We need to be able to set or
> specify the table structure "on-the-fly" thus the reason for calling
> it from a scripting environment or another environment.
> Thanks.
>>
>> Have you looked at DTS, which is included with MSSQL? It has a
>> command-line
>> executable and a COM interface available. See "Data Transformation
>> Services"
>> in Books Online for more details.
>>
>> If DTS isn't suitable for you, you might want to be more specific about
>> what
>> features you require.
>>
>> Simon|||One alternative is a "roll your own" solution. Create linked servers and
just run UPDATE/INSERT/ SELECT INTO statements. The problem is always
making sure you have the relevant drivers on th dev and production
enviroments. The enclosed link gives most of the connection strings needed.

http://www.able-consulting.com/ADO_Conn.htm

I'll warn you before you start this can get messy.

Regards

Adrian

elizabeth wrote:

> Folks here felt that DTS was slow (copied record by record) and buggy
> that is why I was asked to search for something else. What we need is
> fairly basic...to be able to move large amounts of data (in some
> cases > 2 gigs) between a variety of sources (flat files, FoxPro &
> Dbase) into a SQL Server database. We need to be able to set or
> specify the table structure "on-the-fly" thus the reason for calling
> it from a scripting environment or another environment.
> Thanks.
>>Have you looked at DTS, which is included with MSSQL? It has a command-line
>>executable and a COM interface available. See "Data Transformation Services"
>>in Books Online for more details.
>>
>>If DTS isn't suitable for you, you might want to be more specific about what
>>features you require.
>>
>>Simon

Esport databases

I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 server
and SQL server 2000 on a new machine how can transfer the old SQL 6.5
databaes to new SQL server 2000 on a new nachine
Yousuf Khan
Programmer
You can use several methods.
Backup and restore to newserver or Copy both mdf and ldf file to new server
and attach the database or use DTS.
any more question pls reply
hope this will help
Herbert
"Yousuf" wrote:

> I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 server
> and SQL server 2000 on a new machine how can transfer the old SQL 6.5
> databaes to new SQL server 2000 on a new nachine
> --
> Yousuf Khan
> Programmer
|||Herbert thanks for your reply
can you please write me the exact procedure shifting from old server to new
server with upgraded version I am having Tape Device or can i transfer of
import from 6.5 to 2000
Yousuf Khan
Programmer
"Herbert" wrote:
[vbcol=seagreen]
> You can use several methods.
> Backup and restore to newserver or Copy both mdf and ldf file to new server
> and attach the database or use DTS.
> any more question pls reply
> hope this will help
> Herbert
>
> "Yousuf" wrote:
|||U take full backup to ur local server drive. Copy that backup to new server
and using the All Tasks => restore option restore the DB to new server.
For backup and restore refer BOL
Herbert
"Yousuf" wrote:
[vbcol=seagreen]
> Herbert thanks for your reply
> can you please write me the exact procedure shifting from old server to new
> server with upgraded version I am having Tape Device or can i transfer of
> import from 6.5 to 2000
> --
> Yousuf Khan
> Programmer
>
> "Herbert" wrote:
|||6.5 didn't have mdf files, and the storage format was different from the new architecture. So copy
db files or backup doesn't work.
SQL2K has an upgrade wizard that can upgrade from 6.5. Or, use DTS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:CC047EAF-C9A5-4E92-B1E8-4C368296F52E@.microsoft.com...[vbcol=seagreen]
> You can use several methods.
> Backup and restore to newserver or Copy both mdf and ldf file to new server
> and attach the database or use DTS.
> any more question pls reply
> hope this will help
> Herbert
>
> "Yousuf" wrote:
|||Hi,
As Tibor pointed out due to architectural changes you can not DETACH and
ATTACH the databases, as well as BACKUP and RESTORE will not
work.
The best method is to use the SQL server 2000 upgrade wizard.This converts
your Schema, logins, users, data and all other objects to sql 2000.
Every thing automatic.
Detailed steps from books online:-
How to perform a SQL Server version 6.5 to SQL Server 2000 upgrade using a
direct pipeline (SQL Server Upgrade Wizard)
Note To run the SQL Server Upgrade Wizard, you must have an instance of
Microsoft SQL ServerT 2000 already installed on your computer.
To perform a SQL Server version 6.5 to SQL Server 2000 upgrade by named pipe
1.. On the Start menu, point to Programs/Microsoft SQL Server-Switch,
click SQL Server Upgrade Wizard, and then click Next.
2.. In the Data and Object Transfer screen, accept the default selections,
including Named pipe, and then click Next. Verification options are
recommended, but not required. Click Help for information.
3.. On the Logon screen, in the Server name box in the Export server (6.5)
group box, enter the name of the local or remote computer on which Microsoft
SQL Server version 6.5 is installed.
In the Administrator password ('sa') box, enter the sa password for SQL
Server 6.5, and then click Next.
Unless you have changed it already, the default system administrator
password for SQL Server 2000 is blank. Although the SQL Server 2000 default
for the sa password is blank, to conform with best security practices, it
should be changed to a strong password at the first opportunity.
For Import Server (2000), the server name is filled in. Enter the optional
startup arguments, if you want. Click Help for information. When you are
finished setting options, click Next.
4.. In the message box asking if you want to continue, click Yes if you
are ready to upgrade. The SQL Server Upgrade Wizard shuts down SQL Server
6.5 and starts SQL Server 2000.
5.. In the Code Page Selection screen, accept or change the default
settings, and then click Next.
6.. In the Database Selection screen, include the databases to upgrade.
Move any databases you do not want upgraded at this time to the Exclude
list, and then click Next.
Converting all databases is recommended.
7.. In the Database Creation dialog box, select Use the default
configuration or edit the default, and then click Next.
Click Edit to examine and make changes to the proposed disk configuration
within the layout utility. In the Proposed Database Layout box, make changes
as needed. Click Advanced to view Object Details and Drive Summary. When you
are finished, click Accept to return to the SQL Server Upgrade Wizard.
8.. In the System Configuration screen, in System objects to transfer,
select the object types to transfer from SQL Server 6.5 to SQL Server 2000:
a.. Server configuration
Login and remote login registrations and server configuration options
relevant to SQL Server 2000 are transferred as part of the version upgrade.
b.. Replication settings
All articles, subscriptions and publications of each selected database,
plus the distribution database, if any, are transferred and upgraded.
c.. SQL Executive settings
All tasks scheduled by SQL Executive are transferred and upgraded so
that SQL Server 2000 can schedule and run those tasks in SQL Server Agent.
9.. In the System Configuration screen, in Advanced settings, for ANSI
Nulls, select:
a.. Off, if ANSI nulls should not be used when stored procedures are
created. This is the default.
b.. On, if ANSI nulls should be used when stored procedures are created.
10.. In Quoted identifiers, select one of these options, and then click
Next:
a.. Mixed (or don't know), if some of your objects were created with
QUOTED_IDENTIFIER set to ON and others with it set to OFF, or if you are not
sure how they were created.
b.. Off, if all objects should be compiled with QUOTED_IDENTIFIER set to
OFF.
c.. On, if all objects should be compiled with QUOTED_IDENTIFIER set to
ON.
11.. In the Completing the SQL Server Wizard screen, view the summary of
choices you have made. Click View warnings and choices in notepad to open a
text version of the upgrade script. If all options are correct, click
Finish.
The SQL Server Upgrade Script Interpreter screen appears, with information
on the progress of the upgrade.
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eSmyRu7dFHA.1684@.TK2MSFTNGP09.phx.gbl...
> 6.5 didn't have mdf files, and the storage format was different from the
> new architecture. So copy
> db files or backup doesn't work.
> SQL2K has an upgrade wizard that can upgrade from 6.5. Or, use DTS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Herbert" <Herbert@.discussions.microsoft.com> wrote in message
> news:CC047EAF-C9A5-4E92-B1E8-4C368296F52E@.microsoft.com...
>
begin 666 note.gif
M1TE&.#EA# `+`(#_`(2&`,# P"'Y! $```$`+ `````,``L`0 (:C(\(H'S[
68%R0&ED;M7,'[%S2YW#1)VJ;4P``.P``
`
end

Esport databases

I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 server
and SQL server 2000 on a new machine how can transfer the old SQL 6.5
databaes to new SQL server 2000 on a new nachine
--
Yousuf Khan
ProgrammerYou can use several methods.
Backup and restore to newserver or Copy both mdf and ldf file to new server
and attach the database or use DTS.
any more question pls reply
hope this will help
Herbert
"Yousuf" wrote:

> I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 serve
r
> and SQL server 2000 on a new machine how can transfer the old SQL 6.5
> databaes to new SQL server 2000 on a new nachine
> --
> Yousuf Khan
> Programmer|||Herbert thanks for your reply
can you please write me the exact procedure shifting from old server to new
server with upgraded version I am having Tape Device or can i transfer of
import from 6.5 to 2000
--
Yousuf Khan
Programmer
"Herbert" wrote:
[vbcol=seagreen]
> You can use several methods.
> Backup and restore to newserver or Copy both mdf and ldf file to new serve
r
> and attach the database or use DTS.
> any more question pls reply
> hope this will help
> Herbert
>
> "Yousuf" wrote:
>|||U take full backup to ur local server drive. Copy that backup to new server
and using the All Tasks => restore option restore the DB to new server.
For backup and restore refer BOL
--
Herbert
"Yousuf" wrote:
[vbcol=seagreen]
> Herbert thanks for your reply
> can you please write me the exact procedure shifting from old server to ne
w
> server with upgraded version I am having Tape Device or can i transfer of
> import from 6.5 to 2000
> --
> Yousuf Khan
> Programmer
>
> "Herbert" wrote:
>|||6.5 didn't have mdf files, and the storage format was different from the new
architecture. So copy
db files or backup doesn't work.
SQL2K has an upgrade wizard that can upgrade from 6.5. Or, use DTS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:CC047EAF-C9A5-4E92-B1E8-4C368296F52E@.microsoft.com...[vbcol=seagreen]
> You can use several methods.
> Backup and restore to newserver or Copy both mdf and ldf file to new serve
r
> and attach the database or use DTS.
> any more question pls reply
> hope this will help
> Herbert
>
> "Yousuf" wrote:
>

Esport databases

I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 server
and SQL server 2000 on a new machine how can transfer the old SQL 6.5
databaes to new SQL server 2000 on a new nachine
--
Yousuf Khan
ProgrammerYou can use several methods.
Backup and restore to newserver or Copy both mdf and ldf file to new server
and attach the database or use DTS.
any more question pls reply
hope this will help
Herbert
"Yousuf" wrote:
> I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 server
> and SQL server 2000 on a new machine how can transfer the old SQL 6.5
> databaes to new SQL server 2000 on a new nachine
> --
> Yousuf Khan
> Programmer|||Herbert thanks for your reply
can you please write me the exact procedure shifting from old server to new
server with upgraded version I am having Tape Device or can i transfer of
import from 6.5 to 2000
--
Yousuf Khan
Programmer
"Herbert" wrote:
> You can use several methods.
> Backup and restore to newserver or Copy both mdf and ldf file to new server
> and attach the database or use DTS.
> any more question pls reply
> hope this will help
> Herbert
>
> "Yousuf" wrote:
> > I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 server
> > and SQL server 2000 on a new machine how can transfer the old SQL 6.5
> > databaes to new SQL server 2000 on a new nachine
> > --
> > Yousuf Khan
> > Programmer|||U take full backup to ur local server drive. Copy that backup to new server
and using the All Tasks => restore option restore the DB to new server.
For backup and restore refer BOL
--
Herbert
"Yousuf" wrote:
> Herbert thanks for your reply
> can you please write me the exact procedure shifting from old server to new
> server with upgraded version I am having Tape Device or can i transfer of
> import from 6.5 to 2000
> --
> Yousuf Khan
> Programmer
>
> "Herbert" wrote:
> > You can use several methods.
> >
> > Backup and restore to newserver or Copy both mdf and ldf file to new server
> > and attach the database or use DTS.
> >
> > any more question pls reply
> >
> > hope this will help
> >
> > Herbert
> >
> >
> > "Yousuf" wrote:
> >
> > > I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 server
> > > and SQL server 2000 on a new machine how can transfer the old SQL 6.5
> > > databaes to new SQL server 2000 on a new nachine
> > > --
> > > Yousuf Khan
> > > Programmer|||6.5 didn't have mdf files, and the storage format was different from the new architecture. So copy
db files or backup doesn't work.
SQL2K has an upgrade wizard that can upgrade from 6.5. Or, use DTS.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:CC047EAF-C9A5-4E92-B1E8-4C368296F52E@.microsoft.com...
> You can use several methods.
> Backup and restore to newserver or Copy both mdf and ldf file to new server
> and attach the database or use DTS.
> any more question pls reply
> hope this will help
> Herbert
>
> "Yousuf" wrote:
>> I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003 server
>> and SQL server 2000 on a new machine how can transfer the old SQL 6.5
>> databaes to new SQL server 2000 on a new nachine
>> --
>> Yousuf Khan
>> Programmer|||Hi,
As Tibor pointed out due to architectural changes you can not DETACH and
ATTACH the databases, as well as BACKUP and RESTORE will not
work.
The best method is to use the SQL server 2000 upgrade wizard.This converts
your Schema, logins, users, data and all other objects to sql 2000.
Every thing automatic.
Detailed steps from books online:-
How to perform a SQL Server version 6.5 to SQL Server 2000 upgrade using a
direct pipeline (SQL Server Upgrade Wizard)
Note To run the SQL Server Upgrade Wizard, you must have an instance of
Microsoft® SQL ServerT 2000 already installed on your computer.
To perform a SQL Server version 6.5 to SQL Server 2000 upgrade by named pipe
1.. On the Start menu, point to Programs/Microsoft SQL Server-Switch,
click SQL Server Upgrade Wizard, and then click Next.
2.. In the Data and Object Transfer screen, accept the default selections,
including Named pipe, and then click Next. Verification options are
recommended, but not required. Click Help for information.
3.. On the Logon screen, in the Server name box in the Export server (6.5)
group box, enter the name of the local or remote computer on which Microsoft
SQL Server version 6.5 is installed.
In the Administrator password ('sa') box, enter the sa password for SQL
Server 6.5, and then click Next.
Unless you have changed it already, the default system administrator
password for SQL Server 2000 is blank. Although the SQL Server 2000 default
for the sa password is blank, to conform with best security practices, it
should be changed to a strong password at the first opportunity.
For Import Server (2000), the server name is filled in. Enter the optional
startup arguments, if you want. Click Help for information. When you are
finished setting options, click Next.
4.. In the message box asking if you want to continue, click Yes if you
are ready to upgrade. The SQL Server Upgrade Wizard shuts down SQL Server
6.5 and starts SQL Server 2000.
5.. In the Code Page Selection screen, accept or change the default
settings, and then click Next.
6.. In the Database Selection screen, include the databases to upgrade.
Move any databases you do not want upgraded at this time to the Exclude
list, and then click Next.
Converting all databases is recommended.
7.. In the Database Creation dialog box, select Use the default
configuration or edit the default, and then click Next.
Click Edit to examine and make changes to the proposed disk configuration
within the layout utility. In the Proposed Database Layout box, make changes
as needed. Click Advanced to view Object Details and Drive Summary. When you
are finished, click Accept to return to the SQL Server Upgrade Wizard.
8.. In the System Configuration screen, in System objects to transfer,
select the object types to transfer from SQL Server 6.5 to SQL Server 2000:
a.. Server configuration
Login and remote login registrations and server configuration options
relevant to SQL Server 2000 are transferred as part of the version upgrade.
b.. Replication settings
All articles, subscriptions and publications of each selected database,
plus the distribution database, if any, are transferred and upgraded.
c.. SQL Executive settings
All tasks scheduled by SQL Executive are transferred and upgraded so
that SQL Server 2000 can schedule and run those tasks in SQL Server Agent.
9.. In the System Configuration screen, in Advanced settings, for ANSI
Nulls, select:
a.. Off, if ANSI nulls should not be used when stored procedures are
created. This is the default.
b.. On, if ANSI nulls should be used when stored procedures are created.
10.. In Quoted identifiers, select one of these options, and then click
Next:
a.. Mixed (or don't know), if some of your objects were created with
QUOTED_IDENTIFIER set to ON and others with it set to OFF, or if you are not
sure how they were created.
b.. Off, if all objects should be compiled with QUOTED_IDENTIFIER set to
OFF.
c.. On, if all objects should be compiled with QUOTED_IDENTIFIER set to
ON.
11.. In the Completing the SQL Server Wizard screen, view the summary of
choices you have made. Click View warnings and choices in notepad to open a
text version of the upgrade script. If all options are correct, click
Finish.
The SQL Server Upgrade Script Interpreter screen appears, with information
on the progress of the upgrade.
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eSmyRu7dFHA.1684@.TK2MSFTNGP09.phx.gbl...
> 6.5 didn't have mdf files, and the storage format was different from the
> new architecture. So copy
> db files or backup doesn't work.
> SQL2K has an upgrade wizard that can upgrade from 6.5. Or, use DTS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Herbert" <Herbert@.discussions.microsoft.com> wrote in message
> news:CC047EAF-C9A5-4E92-B1E8-4C368296F52E@.microsoft.com...
>> You can use several methods.
>> Backup and restore to newserver or Copy both mdf and ldf file to new
>> server
>> and attach the database or use DTS.
>> any more question pls reply
>> hope this will help
>> Herbert
>>
>> "Yousuf" wrote:
>> I m having WIN NT 4 and SQl server 6.5 i wanted to shift to WIN 2003
>> server
>> and SQL server 2000 on a new machine how can transfer the old SQL 6.5
>> databaes to new SQL server 2000 on a new nachine
>> --
>> Yousuf Khan
>> Programmer
>
begin 666 note.gif
M1TE&.#EA# `+`(#_`(2&`,# P"'Y! $```$`+ `````,``L`0 (:C(\(H'S[
68%R0&ED;M7,'[%S2YW#1)VJ;4P``.P``
`
end

Error: The value was too large to fit in the output column "colName" (60).

Hi All,

I'm trying to transfer data from DB2 Database to SQL Server 2005.

Well, i used the OLE DB Source, the Data Conversion Component and the OLE DB Destination component.

I have five Data flows with this configuration above. But I am receiving an error message from one of them.

Please check below the error message:

"[Source Table TARTRATE [1]] Error: The value was too large to fit in the output column "ADJ_RATE_PCT" (60). "

"[Source Table TARTRATE [1]] Error: The "component "Source Table TARTRATE" (1)" failed because error code 0xC02090F8 occurred, and the error row disposition on "output column "ADJ_RATE_PCT" (60)" specifies failure on error. An error occurred on the specified object of the specified component."

Could you please help me with this issue?

Thanks in advance.

Thiago

The ADJ_RATE_PCT column in your data flow has a defined maximum width. You'll be able to find out what it is by double clicking the data-path leading from the source component.

What has happened is that a value has come in that is bigger than that defined maximum. So, you'll have to increase that maximum in the source component.

-Jamie

|||

Hi Jamie,

Thanks for your answer, but i still dont have a solution for this.

I tried to change the field width but i still have the same error message.

I think it is related with the field type. I received the same error message in another package and the field type is the same ( numeric , Precision 4 and Scale 2 ) as the first one.

I will continuing trying to figure out what is happening.

Thanks in advance.

Thiago

|||My guess is that, like Jamie said, a value is coming in that is bigger than the type. Based on the error message, and the type, it sounds like the value probably has a precision larger than 6. Have you tried increasing the precision (and possibly scale) of the output column in the advanced editor (inputs and outputs tab) of the source component?|||

Hi All,

Guys, thanks for your answer but I just don't know what to do now.

I changed the Precison (to 5) and Scale (to 3) in the Adavnced Editor following this sequence: Advanced Editor --> Input and Output Properties --> DataReader Output --> External Columns --> Select the column then change these two Data Types Properities: Precision and Scale. I tried to re-run the package and i still have the error message.

I saw that there is another "option" in the DataReader output menu called "Output Columns". I can't change any property in this menu. I guess these columns ( in the Ouptut Columns menu) are the return types from the source table ( im using a "select" command in a DB2 table ).

Another detail: in the "Output Columns" menu, the field that is returning error, has the precision 4 and Scale 2 ( remember: i cant change these values, they are automatically assigned by the component )). I think these values are comming from the source table. Am i right?

Thanks in advance for your help and atention.

Regards.
Thiago

|||

Hi Thiago,

Yes, in the DataReaderSrc you cannot change the properties of the output columns -- they are fixed at what the provider said the metadata was for the source column. Changing it in the External Columns will have no effect...

Your original post said you used the OLE DB Src -- if that is correct, you CAN change these properties there... Can you give that a try?

Thanks,
Mark

|||

Hi All,

Finally I find out what were happening in my application.

It was not related with the SQL2005 but with the DB2 ODBC Driver.

Follow below the instrunction how to fix this error in your DB2 ODBC Driver:

When you reconfigure your connection ( in the ODBC ), you have an Advanced button. So, you should click there and look for a Service Tab. In this service tab you have some "know workarounds".
There are two workarounds in this tab ( called PATCH 1 and PATCH2). In the second patch you have an option with this description: "Always use period for decimal separator in character output". You MUST select this option then type "15" in the value text box.

After that, just click ok and your DB2 ODBC driver will be configurated.

Thank you all for your answers.

See ya.

Thiago