I have a number of SSIS packages (package deployment model) running on their own ETL server. I am trying to modify several of them to use the always on secondary via the LISTENER, but having trouble when I try to debug the package. Especially if I am using SQL Server security for the login.Most of the searches I've done, only seem to discuss the SSISDB catalog, which is not what I'm after, since I want to be using the secondary to retrieve production information.It seems to work fine (adding the applicationIntent, sufficient timeouts) if I use integrated security, but when I use the SQL Server security, it fails to log in to the listener. It also doesn't matter if I use OLE DB or ADODB, both fail. Using Windows security to connect defeats the purpose of protecting my data based on SQL userid and roles.I'm using Visual Studio 2013, and SQL Server 2014. If anyone has been successful at this, I'd like to know what kind of hoops were jumped through.Thanks,Luther
↧