October 15, 2013 at 7:06 pm
I've read several posts and blogs on the subject. I think I have a strategy. Here's how I came by it...
My users do not have the DTS environment on their systems. That means the object model is at best inconvenient.
I need to pass parameters to the SSIS package, so an ADO.net call to a stored procedure could work, but I think I like option 3....
I think I'll set up a SQL Server table that contains the (zero or more) file names that are ready to be processed, along with any other parameters, and then, when my user (who has permission to do this...) imports the data into a flat file, the program doing that will post the filename (and any other parameters) to the SQL Server table. Then, I'll set up a scheduled agent on SQL Server that checks for new entries in the table and fires up the appropriate SSIS package....
That make sense to you all? Or should I just do option 2 with the ADO call to a stored procedure that sets off the SSIS package. It's pretty much asynchronous either way, I think...
What do you think?
Jim
October 16, 2013 at 1:36 am
If it's SSIS 2012, you can very easily start SSIS packages with parameters using stored procedures, so I would look into that route. I believe you can also run the SSIS packages synchronously if you'd like.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 16, 2013 at 8:07 am
Koen, do you have any references I could read to get me started? It is SS2012.
Jim
October 16, 2013 at 12:48 pm
Deploy and Execute SSIS Packages using Stored Procedures
Step by step of executing SSIS 2012 package through stored procedure
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply