Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am testing different configurations for loading data from a remote SQL server using SSIS. In a clustered situation SSIS seems slower to speak to the local clustered SQL instance when compared to a non clustered local SQL instance. It looks like any scenario where SSIS speaks to a clustered SQL instance; the communication occurs through the network regardless if the SSIS instance is local or not. Is this true?

In my current scenario, SSIS 2008 R2 is running on a node with clustered SQL Server 2008 R2 instances. It seems to communicate with the clustered instance through some network interface even if they are both on the same Node. Oddly, I cannot identify which interface it is.

Here is the general layout:

Cluster Node 1 physical IP

SQL Server "sql2008" instance name has an IP

SQL Server Instance is on Node1

Remote SQL server source for SSIS IP

The SSIS Load transfer rate seems slow. The SSIS network session to the remote SQL server source appears under the Network section in Resource Monitor.

Image: DTExec.exe

PID: 8864


Send (B/sec): 968

Receive (B/sec): 1,682,022

Total (B/sec): 1,682,990

But the SSIS for loading also appears in network. It seems to run from the local node to to the destination SQL server IP through network communication because DTexec shows up under Resource Monitor - Network as speaking to the Destination SQL server IP.

Image: DTExec.exe

PID: 8864


Receive (B/sec): 120

Send (B/sec): 20,300,868

Unfortunately when I use network monitor to see the traffic, the dtexec traffic from source appears but the load activity does not seem to appear to be using any of the network interfaces and cannot be seen.

When running this same package (against the same unchanged source) with a less powerful non clustered box, the SSIS package runs 2x faster speaking to a local instance and the Dtexec load process does not appear in the Network section in Resource Monitor. Only the Dtexec network session for the source process appears and is the same speed.

Is the missing Network traffic on the non clustered scenario giving me the boost or am I looking at something misleading?

share|improve this question

Your SQL Server does have a different IP address from you SSIS. The clustered SQL will alway get traffic from the "virtual network address", ip=101 in your case, even if it is being hosted on "Node A" and you have a program running on "Node A" , SSIS ip=100 in your case.

That is the way clustering works.

BTW the virtual IP is controled by the Clustering service and is bound to one of the network cards on Node A or B which ever is hosting the clustered SQL Server

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.