I have been handed a Visual Studio project containing about 30 ETL's. The connection managers use aliases instead of specific server names, which is good. However, when I try to set up matching SQL Server aliases on my PC, using SS Configuration Manager, I can set up the aliases, but I can't actually access them in SSIS. When I try to create a new connection manager, the aliases aren't displayed in the list, nor do the exising connection managers automatically adjust & work now that there are matching aliases (if I try "test connection" it fails.)
On my PC, SS 2008 is the default SQL Server instance. SS 2012 is a named instance, basically localhost\SQL2012. The databases required are in the localhost\SQL2012 instance. I set up (both 32 & 64 bit) aliases as:
CSDW_DWTarget - alias
tcp - connection type
localhost\SQL2012 - server
If I set up a brand-new SSIS connection manager, simply using <PC_name>\SQL2012 - not an alias - that works, but I'd prefer to set up an alias that matches the connection managers already in the project.
Thanks for any suggestions,