February 23, 2011 at 6:17 am
Hey All,
I have an interesting question that I just dont know the answer to and, well, this is the best palce to find answers.
I have a dedicated SSIS server. I deploy all of my packages to this server and no data is stored there except for my runtime logs. Let me run a small scenario, and if you could, can you help me answer my question below:
I have my SSIS server. A package on there moves data from Server A to Server B and does some manipulations along the way.
My question is this, does any of the data from Server A ever reside on my SSIS server, for any length of time, because the package is deployed there? Does the data flow task cause any data to move through my SSIS server?
Thanks in advance to anyone who can help me on this.
February 23, 2011 at 7:48 am
Yes, all data used within the package such as the data source and look-up transformations reside within the RAM, memory cache, or persistent cache on the SSIS server.
If I extend your logic, thus concern, you might wonder if there are data security or compliance issues. As long as you are not persisting the data to disk and as long as that data is not accessible outside of the SSIS container, there are not security or compliance concerns (assuming you have secured your package configurations and other standard SSIS security stuff).
February 23, 2011 at 8:23 am
Thanks for the reply. This is very interesting, and I knew that this was the place to find the answers.
It is troubling to me though that the data is held on the SSIS Server for any length of time, regardless of security.
Thanks
February 23, 2011 at 9:47 am
Why?
I implemented an Integration (SSIS) Server at one of my previous places and its still going strong.
February 23, 2011 at 10:01 am
If the data is going from one server to another (A to B), then the data also exists for some period of finite time, on any routers/switches in between them, in the network cards on both servers, and on the cables it is being transmitted through. Does that also bother you?
(If it's a data security issue, then router-hacking is much more likely to be an issue than SSIS holding data in RAM.)
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 23, 2011 at 10:38 am
The only thing that bothers me is what the SSIS server might hold, regardless of the amount of time its held. I'm not worried about what is being transfered from A and B or where that data might happen to be at any point in time, its only what gets held on the SSIS Server.
Its more of a contractual obligation thing more than anything else.
Thanks all!
February 23, 2011 at 11:28 am
The only way to avoid that will be to put the SSIS engine and package on one of the two servers. Any method that involves a third server will end up with data, however ephemeral, on that third server.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 23, 2011 at 12:13 pm
Thanks!
Exactly what I was looking for!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply