Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

how to make the one Filewatcher to wait till another one finishes it work..like any sort of queue mechanism

$
0
0

Hi

We have the following scenario for FileWatcher Implementation.

We have a folder in share drive lets say (\\ussby302\MABCD\).An UI application lets say a windows or asp.net application place .txt,.csv or .xls  file in the share folder \\ussby302\MABCD\ at any point of time.

We need to develop a SSIS Package which needs to process the .txt file which has been placed in the folder using a temp table in Sql Server before processing the file the ssis package will have to  truncate the table and then it will start the processing.

Similarlly we need to develop a SSIS Package which needs to process the .csv file which has been placed in the folder using a temp table in Sql Server before processing the file the ssis package will have to  truncate the table and then it will start the processing.

Similarlly we need to develop a SSIS Package which needs to process the .xls file which has been placed in the folder using a temp table in Sql Server before processing the file the ssis package will have to  truncate the table and then it will start the processing.

the problem here is while the package which processes the .txt file is processing using the temp table in that time if an .csv got placed by the ui appliation in the share folder then package which corresponds to .csv will start running so it may truncate the temp table while it been used by the .txt package.

So we may end up in losing data.because both the package will try to use the temp table

So we need to find out any sort of queue mechanism to resolve this..

Like if any package uses the temp table other package  has to wait ...and it has to start working after that...

how can we do that...


ilikemicrosoft


Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>