>I would export Oracle Data into text file and import using bulk insert to
>sql
> server.
> DTS is slow compared to bulk insert or bcp.
>
> - Goutam
>
>
> "Shawn" wrote:
>
>> I am trying to setup a DTS job that must run every 30 minutes and pull
>> 3.5
>> million rows from an Oracle database into our SQL2k database. The job
>> runs
>> fine (2 minutes), but consumes a TON of network bandwidth on the network
>> card and we have a VERY bandwidth sensitive application that connects to
>> the
>> db. Anyone have an idea how to deal with this?
>>
>>
>>

> I am trying to setup a DTS job that must run every 30 minutes and pull
> 3.5 million rows from an Oracle database into our SQL2k database. The
> job runs fine (2 minutes), but consumes a TON of network bandwidth on
> the network card and we have a VERY bandwidth sensitive application
> that connects to the db. Anyone have an idea how to deal with this?
>

> Yeah, I was really thinking to go that way first, but we are trying to
> keep things as simple as possible.
>
> Also, I did try running the same job from a test SQL Server to our
> Prod. server to see if Oracle was the problem, but I get the same
> bandwidth problem. But, the job does run faster...
>
> "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
> news:f0343b0312be08c7f52412a3c750@msnews.microsoft.com...
>
>> Hello Shawn,
>>
>> The OLEDB drivers between O and SQL Server are notoriously slow. A
>> lot of
>> people pump to text file, FTP then use BULK INSERT. This is the way
>> I
>> would approach this problem.
>> There are 3 very distinct steps and whilst there are 3 vs 1 step in
>> the
>> other direct trabsfer solution, these steps are simple and clear in
>> purpose.
>> Allan
>>
>>> I am trying to setup a DTS job that must run every 30 minutes and
>>> pull 3.5 million rows from an Oracle database into our SQL2k
>>> database. The job runs fine (2 minutes), but consumes a TON of
>>> network bandwidth on the network card and we have a VERY bandwidth
>>> sensitive application that connects to the db. Anyone have an idea
>>> how to deal with this?
>>>

"Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
news:f0343b0312be08c7f52412a3c750@msnews.microsoft.com...
> Hello Shawn,
>
> The OLEDB drivers between O and SQL Server are notoriously slow. A lot of
> people pump to text file, FTP then use BULK INSERT. This is the way I
> would approach this problem.
> There are 3 very distinct steps and whilst there are 3 vs 1 step in the
> other direct trabsfer solution, these steps are simple and clear in
> purpose.
>
> Allan
>
>> I am trying to setup a DTS job that must run every 30 minutes and pull
>> 3.5 million rows from an Oracle database into our SQL2k database. The
>> job runs fine (2 minutes), but consumes a TON of network bandwidth on
>> the network card and we have a VERY bandwidth sensitive application
>> that connects to the db. Anyone have an idea how to deal with this?
>>
>
>