Hi,

I have an ETL job that takes a long time (around 12 hours to run). The
extraction and transformation are done in a linux box and the data is loaded
into SQL Server.

SQL Server has the default network packet size which i believe is 4096
bytes. Would the ETL job benefit if I increase the network packet size to say
32k?

How can I monitor the current packet size usage?

I am sure there is scope for the ETL job as such to improve and working on
quite a few of them. But I was reading about this and thought whether this
might also .

Thank you.

Regards,
Karthik

Hi Burt,

Thank you for the response. The network pipe is 1 gbps.

The approximate amount of data would be 80 - 100 GB a day.

The hard disk seems to be in good shape and the tables aren't too badly
fragmented also. There is also sufficient disk space available (at least for
a minimum of 10 days i.e. 800 - 1000 GB free at any time)

Regards,
Karthik

"burt_king" wrote:

> *Might* is correct. How much data are we talking about and how big is
> the network pipe? 100mbps, 1gbps? Something else.
>
> I'd certainly verify the congestion isn't the hard drives first.... that's
> nearly always the culprit in large data loads.
> --
> DatabaseAdmins.com
> Remote DBA services
>
>
> "Karthik" wrote:
>
> > Hi,
> >
> > I have an ETL job that takes a long time (around 12 hours to run). The
> > extraction and transformation are done in a linux box and the data is loaded
> > into SQL Server.
> >
> > SQL Server has the default network packet size which i believe is 4096
> > bytes. Would the ETL job benefit if I increase the network packet size to say
> > 32k?
> >
> > How can I monitor the current packet size usage?
> >
> > I am sure there is scope for the ETL job as such to improve and working on
> > quite a few of them. But I was reading about this and thought whether this
> > might also .
> >
> > Thank you.
> >
> > Regards,
> > Karthik

*Might* is correct. How much data are we talking about and how big is
the network pipe? 100mbps, 1gbps? Something else.

I'd certainly verify the congestion isn't the hard drives first.... that's
nearly always the culprit in large data loads.
--
DatabaseAdmins.com
Remote DBA services


"Karthik" wrote:

> Hi,
>
> I have an ETL job that takes a long time (around 12 hours to run). The
> extraction and transformation are done in a linux box and the data is loaded
> into SQL Server.
>
> SQL Server has the default network packet size which i believe is 4096
> bytes. Would the ETL job benefit if I increase the network packet size to say
> 32k?
>
> How can I monitor the current packet size usage?
>
> I am sure there is scope for the ETL job as such to improve and working on
> quite a few of them. But I was reading about this and thought whether this
> might also .
>
> Thank you.
>
> Regards,
> Karthik