October 17, 2015 at 8:29 am
So I am very new to SSIS and I have a question regarding the WMI watcher.
I have several import processes running across around 20- 30 files. These are all performed by various applications or ETL packages that I do not have access to change. I want to build a IS package to monitor these folders and when detecting the file, writes it to a SQL table. I have got this to work on my local machine but soon as I try to do a network path \\servername\path it will fail. I know that mapping a drive will work but this is not an option with so many locations to monitor. It was mentioned that I can script task this but I am no vb/c# dev so my question is, can I do this any other way? I have all the network locations in a table ready to scoop up.
October 18, 2015 at 8:25 am
6660999 (10/17/2015)
So I am very new to SSIS and I have a question regarding the WMI watcher.I have several import processes running across around 20- 30 files. These are all performed by various applications or ETL packages that I do not have access to change. I want to build a IS package to monitor these folders and when detecting the file, writes it to a SQL table. I have got this to work on my local machine but soon as I try to do a network path \\servername\path it will fail. I know that mapping a drive will work but this is not an option with so many locations to monitor. It was mentioned that I can script task this but I am no vb/c# dev so my question is, can I do this any other way? I have all the network locations in a table ready to scoop up.
The standard way of doing this would involve the use of a UNC path, as you initially suggest. When you say that 'it will fail', can you provide more detail? What error message do you get?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply