The general architecture remains like this:
- Feeds arrive from the source system in case if the source is some legacy system like mainframe. Also there may be jobs which fetch data from the OLTP system via push/pull methodology and then it's staged into a text file.
- Feeds are guided to the target ETL directory through some schedulers, for ex. Autosys
- A File Watcher remains on the ETL system which detects the presence of the file/feed, picks up the same and then after ETL, the same gets loaded to either a staging DB or to the destination DB.
- Generally it's BCPed to the staging DB, and after application of business rules, it's loaded into the destination DB or data warehouse.
In SSIS what I have seen missing is the File Watcher task. It needs to be implemented by either infinite looping to watch for a file (it's a very bad methodology of implementing the functionality) or using WMI for the same, or finally thru a work-around by signalling mechanism or through scheduling.
I found a similar implementation of the same in SQLIS, where a component called "File Watcher Task" is available. But seems like it has serious limitations and is also not bug free. I am just assuming this from the comments and components description. May be Microsoft should make this functionality available through some service packs or at least in the next version.
No comments:
Post a Comment