Hi We are a team with 3 members (M1,M2 and M3)working on same set of ssis packages without source control... Each and every one will connecte different datasource (different connection)..but the datasource schemas are same so nothing to worry about that.. Problem here is when the M1 gets package from M2 and if he opens the any package(which has connection created in datasource and which added in package connection manager)...the database gets locked bcoz connection differs .We are using db2 database.. So i deleted the ConnectionManager from the code before opening the package <DTS:ConnectionManager> <DTS:Property DTS:Name="DelayValidation">0</DTS:Property> <DTS:Property DTS:Name="ObjectName">DB2CP</DTS:Property> <DTS:Property DTS:Name="DTSID">{3088AC8F-2943-4A82-9733-408A89ACAE2D}</DTS:Property> <DTS:Property DTS:Name="Description"></DTS:Property> <DTS:Property DTS:Name="CreationName">OLEDB</DTS:Property><DTS:ObjectData><DTS:ConnectionManager> <DTS:Property DTS:Name="Retain">0</DTS:Property><DTS:Password DTS:Name="Password" Sensitive="1" Encrypted="1">HoAwE/Cl+XrMAAAADZzMqeVzNpC/Sd+FeMGfd7nE21LV2yQQAAAA</DTS:Password> <DTS:Property DTS:Name="ConnectionString">Data Source=DB2CP;User ID=XYZ1233;Provider=IBMDADB2.DB2COPY1;Persist Security Info=True;</DTS:Property></DTS:ConnectionManager></DTS:ObjectData></DTS:ConnectionManager> <DTS:ConnectionManager> but what happened is source connection wont be there in the package so all the query and meta data get lost.... how to mange this situtation... ilikemicrosoft

Try tying the connection manager to a configuration file. Each person would have his or her own configuration file with the connection appropriate to his or herself. I believe that the configuration is loaded first and then the connection manager is validated. If that doesn't work, try disabling validation on the connection manager (DelayValidation property equal to true).Russel Loski, MCT, MCITP Business Intelligence Developer and Database Developer 2008 Blog: http://www.bidn.com/blogs/RussLoski/ Twitter: @sqlmovers

Listen to Russ's advice. You ought to use the configuration. Your approach to deleting the connection manager is wrong because editing the package code (XML) from outside BIDS is potentially a package wrecking endeavor. Or even deleting the component at the package designer level should not be done just for the sake of amending the connection string. It can be easily parametrized via the configuration.Arthur My Blog