November 18, 2019 at 10:18 pm
Create an SSIS package that processes the file;
whether the procedure calls CLR to process the file, or you load the file contents into a SQL table via that SSIS package , and then call the stored procedure is up to you.
then you can have a job that calls that SSIS package every x minutes, across a schedule when you might expect the file.
(ie i expect the file M-F somewhere between 4 am and 7 am, execute the package every ten minutes.)
you use a foreach loop to go through all files int he folder, even if you expect there to be only one.
that way, no files means the package exits quickly when no files found.
Lowell
November 19, 2019 at 2:39 pm
You allow an app to write files to your SQL Server? I don't allow that. It have people write their files to a different box and then give SQL Server the privs to see the drive(s) on that box.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply