Hi Everyone, I am the owner of a SQL Server 2008 R2 database and need to run SSIS packages daily to populate the data. The problem is that my sysadmin will not give me access to save an SSIS package on the SQL Server or File System. Long story short - I have to create a service request ticket and wait a couple of weeks for my packages to get uploaded to the server. My question is: Can I save my SSIS package(s) in a SharePoint document library and have the sysadmin point the schedule job to the network path of the SharePoint library? (ie. \\mysite.company.com\SSISPackages\Package.dtsx). I tried this on my local machine and it works fine - do you see any issues with using SharePoint to store the package files? Thank You Sam

Thank you for your response Arthur. I contacted my sysadmin and he is OK with this method. What happens if the connection to SharePoint drops? Do you know if the package gets copied to the local machine and then closes the connection? One of my packages run for 3 hours and I don't want SSIS to read the package for the whole duration...just in case IIS times out within the 3 hour window.

1) What happens if the connection to SharePoint drops? 2) Do you know if the package gets copied to the local machine and then closes the connection? > 1: You are on a mercy of the connectivity, afterall, you were seeking a temp solution until you get a permanent one, right? >2: Yes, to %temp% normally/by default; if the package is not large + you are on a good bandwidth this will be done very fast.Arthur My Blog

As long as you do not breach any security or violate any of your company policies this is fine, to run SSIS you need the SSIS engine installed, by calling it from a remote location the package gets copied to the local machine and executed. So all is valid from this point of view and you have tested that this method works already.Arthur My Blog