I am writing an SSIS package that will extract data from a SQL Server database. One of the data flow tasks connects to a database that I cannot access except with Windows Authentication -- the administrator is not willing to create a userid for my use under SQL Server Authentication -- though he will create a Windows service account login if I need one.
My normal Windows logonid does have access to the database, so I am able to connect right now, and the package works fine. But I intend to load the package on a server and run it as a job under SQL Server Agent. When I do that, is it possible to create a Windows logonid different from the one that will run the package itself? Looking at the interfaces for creating Connection Managers, I don't see a likely way to do this. Any suggestions?