I've developed a SSIS ETL job/workflow to scan for new files in a folder and load the data from the new file into a SQL Server table. This job basically implements searches for a file with a predefined file name pattern in a predefined folder location. I followed all the steps mentioned here. However, the tricky part is that my company uses Box.com for file storage and the particular folder where the SSIS job has to search for new files is on Box.com. When I use my local Box-Sync Path and run the job on my local machine, I am able to execute the entire package successfully and load the new data into the required table. However, when I deploy this job in the SSIS Catalog and try to run it from the Server, the job fails as the SQL Server is unable to resolve the local Box-Sync Path that's specific to my machine.
Could anyone suggest which path I should be using to get rid of this error and schedule the job successfully on the Server.
TIA.
You will need to create a Box-Sync path on a server that your SSIS agent has access to and use either a UNC path to that Sync folder, or a path that is local to your SSIS Server.