I changed one data source settings in my SSIS project to use Windows Authentication instead of SQL Authentication. This data source is used to create connection managers in all SSIS packages. Soon after the data source was changed, when I opened any package using the connection manager that is based on this changed data source, I got an alert message box like the one given below showing different connection strings in data source and package connection manager. That's understandable (why can't VS 2005 do this silently or give an option to let this happen silently? that would be nice.). Here is the problem.Even after both data source and connection manager are synchronized, still the same message box keeps on coming when ever I open any affected package (about 20 packages!). It is very annoying as you can see that old and new connection strings ARE IDENTICAL, still VS 2005 is not able to recognize this. I installed VS2005 SP1 even before I ran into this problem. I asked my friends to open this project and check the behavior on his machine. Same thing. Is this a known bug? How to fix this problem? Thanks for your help. ===== Message box "Synchronize Connection Strings" (VS 2005 status bar shows "Performing post package load operations"): This package contains at least one connection which is based on a datasource. The connection string for conenctions and data sources listed below are currently not identical. Connection strings of connections will be updated to reflect those on the datasource. Connection: SqlServer.NET.HBI_DW.hbiuser Data source: SqlServer.NET.HBI_DW.hbiuser Old Connection String: Data Source=SDAL1060DB;Initial Catalog=HBI_DW;Integrated Security=True; New Connection String: Data Source=SDAL1060DB;Initial Catalog=HBI_DW;Integrated Security=True; =====

It sounds like a bug although having never used Data Sources I can't be sure. If I were you I would get rid of data sources altogether. Just use Connection Managers with configurations. -Jamie

I quit using data source views long time ago after experiencing the same issue you are reporting. I realized SSIS copies the datasaource view info inside of each package; creating the sync issue each time something changes in the DS definition.

Thanks for the feedback. After going thru extensive trail and error kind of work, I stopped getting this prompt. I did not keep track of the sequence of things. But when I edited configuration on one package which uses the above connection manager, that did it! After this point, refreshing the datasource change to connection managers in other packages was smooth (one time thing) with out the unwantedrecurring "synchronizing connection strings" prompt. No clue why it behaved this way! I agree with you on getting rid of data sources to save time.Microsoft should do better in replicating data source change to connection managers by giving an option to choose silent refresh besides fixing any outstanding bugs like the one I encountered.

Shan Metla wrote: Thanks for the feedback. After going thru extensive trail and error kind of work, I stopped getting this prompt. I did not keep track of the sequence of things. But when I edited configuration on one package which uses the above connection manager, that did it! After this point, refreshing the datasource change to connection managers in other packages was smooth (one time thing) with out the unwantedrecurring "synchronizing connection strings" prompt. No clue why it behaved this way! I agree with you on getting rid of data sources to save time.Microsoft should do better in replicating data source change to connection managers by giving an option to choose silent refresh besides fixing any outstanding bugs like the one I encountered. That sounds like good feedback. You should submit it at connect.microsoft/com/sqlserver/feedback

I am also getting the same error and I can not get rid of it. I have 5-6 pkgs that uses the same Connections so I created DataSourceat Solution Level and in Connection manager used "New connection from DataSource" It is annoying and I can't seem to find a way to get rid of this.. I edited all the pkg config file and still.....

Easiest way to get rid of it? Delete the connection managers, then recreate them without using the data source.

I too ran into this issue. Here is what I discovered. The <project>.dtproj project file is an xml file which contains connection string information about each of your Data Sources. So, if you change the data source information in a package but not in the project file, you will get the "Synchronization..." dialog everytime. Here's the really cool part. So what I have done is created a "Configuration" in the project for each of my deployment scenarios (development, QA, staging, production.) When I created the configuration I copied the previous configuration. Next, I opened the <project>.dtproj file in notepad (or your favorite xml editor because there is no IDE that enables you to work with the details of the configuration) and modified the connection strings for each configuration to match my deployment scenario. Now all I need to do to switch connections in my data sources is to change my configuration for my project!

There is an even easier way. Just delete the value in the DataSourceID property. That seems to break the link to the data source.

i guess it is not connection manager configuration issue. Delete and Recreate is not a good solution. I guess SSIS has cache issue. Once we change the connection manager it will not refresh. Anyone know how to clear cache memory for SSIS packages in Visual Studio. sometimes if we restart system it works but sometimes even that will not help.Please provide me option to refresh cache or buffer so that it will point to new connection.Thanks in advanceRamana CheripallyRamana

i guess it is not connection manager configuration issue. Delete and Recreate is not a good solution. I guess SSIS has cache issue. Once we change the connection manager it will not refresh. Anyone know how to clear cache memory for SSIS packages in Visual Studio. sometimes if we restart system it works but sometimes even that will not help.Please provide me option to refresh cache or buffer so that it will point to new connection.Ramana

Using SQL Server 2008 and this issue is still present. Is this 'normal' behaviour or what. I supposed that Microsoft should have solved this. Not using datasources doen't seem a solution to me. Why is it developed like this way anyway?Greetz,Hennie

Can you tell me where the DataSourceID property is that I'm suppose to delete? This seems to work, but it's a pain to do for every connection manager. I found you can also, repoint to a different data source, then point back and that fixes as well. Neither are good solutions.

Any resolution on this? I have the same problem and a huge solution with tons of connection managers and data sources all pointing a master config project where I should be able to edit them all. Thanks in advance if you have anything.

Hi Jamie, Could you explain how you do that. At this moment I'm having the same problems with the "Synchronize Connection Strings" Msgbox. Regards, Mark