1. Choose “Do Not Save Sensitive Information,” at the project and package levels.
2. Instead, submit the credentials at runtime through the new Project Parameters feature in SQL Server 2012.
We’ve been running SSIS with CozyRoc that way for nearly a year now and it has been without any issues.
You just select your project connection in the Connection Manager at the bottom of your package screen, right click and choose Parameterize. You can do the connection string and then do one for the password. These can then be entered when you schedule the job. This should complete avoid the SALT error when that username and password are saved directly in the connection manager.
On the other hand, it may have been fixed since CU 6.
Here is the current list of SP1 CUs for 2012 that have been released.
http://support.microsoft.com/kb/2772858
--
You received this message because you are subscribed to a topic in the Google Groups "COZYROC" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cozyroc/VN0m6qihKWc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cozyroc+u...@googlegroups.com.
To post to this group, send email to coz...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cozyroc/a8a91030-a37d-4fc8-a330-0820a85f227c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.