January 14, 2009 at 6:49 am
Hi,
I will try to be as clear as possible.. with as much as i know.
We have a clustered SQL Server 2005. As of now we have created a SSIS package and this package is set up and run as a job under sql server agent on one server.
I need to find out which ip runs the SSIS package. Is it the clustered virtual ip or the physical ip of the one of the server?
To put as a different way, is there any variable / property in SSIS through which i can get the ip of the machine that its running.
Note:
IP is required to provide FTP access to a unix machine.
We are not concerned if SSIS is made clustered or not(Our SQL Server is...). Just need to find the IP.
Thanks,
Sameer
January 14, 2009 at 6:57 am
The system variable "MachineName" can give the name of the machine running the package, but I don't know how to get the IP address. May be there is one or the other way out for it.
--Ramesh
January 14, 2009 at 9:38 am
Sameer Sait A (1/14/2009)
Hi,I will try to be as clear as possible.. with as much as i know.
We have a clustered SQL Server 2005. As of now we have created a SSIS package and this package is set up and run as a job under sql server agent on one server.
I need to find out which ip runs the SSIS package. Is it the clustered virtual ip or the physical ip of the one of the server?
To put as a different way, is there any variable / property in SSIS through which i can get the ip of the machine that its running.
Note:
IP is required to provide FTP access to a unix machine.
We are not concerned if SSIS is made clustered or not(Our SQL Server is...). Just need to find the IP.
Thanks,
Sameer
You have to write script using the API described here. If you have additional related questions, ask them here[/url] because this forum is only for SSIS specific questions.
January 14, 2009 at 10:14 am
Obviously on a cluster you want the package to keep on working on failover, in which case you may want to store the package in the msdb, rather than in the file system. In this way it will run from the virtual IP, if you have it set up in another way in the job then the IP may be different.
If you are working with storing files from the package I would store them away from the cluster so that they are available when the cluster works from any node, then your FTP job need not be concerned with any cluster issues.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply