Dear all,
I would like to hear point of views, thoughts and ideas about the following request.
As some of us would have seen from a couple a days ago I’ve been setting posts one after one in order to obtain some answers about our business basis.
We’ve got a service running all day long (to accomplish this it was wrote by Visual Basic 6.0) which is checking up a file structure system for a several requirements such a verify if exists a .nul or .txt in each folder and therefore fires a DTS package. Up to here that’s fine, that system works amazing and even is be able to run till three packages at the same time. 400 Dts are scheduled this way and 100 are scheduled by Agent.
Problem comes naturally with SQL2005 where such control is not possible (it seems so) from old tools belonging to Visual Studio 6.0 because the aforementioned version uses assemblies instead of dll, bla,bla.
Keeping in mind that .NET is not possible for reasons that going beyond of any technical matter or whatever I’ve thought do that service by SSIS. A big SSIS running forever. Its responsabilities might be:
1-Look in each folder for the criteria specified in the scheduling of that SSIS
2-Launch a specified SSIS in the case that criteria has matched.
3-Update SQL tables with LOGS, times, executions, etc,
4-Look again
The point 3 will be visible from our Intranet via ASP 3.0 pages as currently we do.
Pros and cons?
Sorry for this painful request but I don’t believe that such issue can be of that kind of odd issues that nodoby suffer in its organizations.
Who else is needed for answers?
Thanks a lot for your time,
I'm not quite sure what your question is. Are you saying you want to run a SSIS package forever that simply keeps looping whenever a file is found? I don't see a problem with that. it would be interesting to see how it goes.
-Jamie
|||When finds a Jamie.Nul file in d:\server25k\a\ launch SSIS package B and then would delete that .NUL.
Sensible information attached in that SSIS launched as flat file for example, accounts info would be stored in a backup folder. After one execution come back to verify and so on
No comments:
Post a Comment