At 25:29, the connection managers at the Package level do not have all the same properties. They have different GUIDs and are in fact physically separate. This is why SSIS does not treat them the same when one is promoted to the Project Level.
The information in this video about another Developer being able to determine the Sensitive password values is not entirely correct. This depends on the Protection Level of the project and its packages. We can either encrypt by password or by User Key. If User Key, then only the original person can see the password. If Password, then the Developer must know the Project Password in order to get to the clear text version of any Sensitive values within that Project.
![ทุกครั้งที่หลับตา (Lucid Dream) - AYLA's [ Official MV ]](http://i.ytimg.com/vi/4i1OBAQyv58/mqdefault.jpg)
At 25:29, the connection managers at the Package level do not have all the same properties. They have different GUIDs and are in fact physically separate. This is why SSIS does not treat them the same when one is promoted to the Project Level.
Many Thanks!
The information in this video about another Developer being able to determine the Sensitive password values is not entirely correct. This depends on the Protection Level of the project and its packages. We can either encrypt by password or by User Key. If User Key, then only the original person can see the password. If Password, then the Developer must know the Project Password in order to get to the clear text version of any Sensitive values within that Project.
just a bit blurry in full screen.