November 10, 2009 at 9:02 am
When I use visual studio to build and deploy SSIS packages and make a change to an existing package, do I have to update SQL Server Jobs that are scheduled that use previous versions of the package?
November 10, 2009 at 9:05 am
Not if you gave it the same name.
- 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
November 10, 2009 at 9:26 am
Thanks GSquared.
I redeployed my solution, but I did notice that all the reference packages reverted to providing a connection string with no Password=<password> attribute. Is there a way to deploy packages so that username and passwords get published to?
November 10, 2009 at 9:30 am
I'm not sure. I always use integrated (Active Directory) security, so I've never run into that.
- 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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply