Run SSIS Package using Microsoft.SqlServer.Dts.Runtime or Sql Server Jobs
-
Hi, I have and SSIS Package, my lead wants me to create a C# application that sets Variables, Connections and everything properly and executes the package, I did that, I even have written OnError event and logged the Error why SSIS failed to execute. As far I saw there is no difference between my Application and SQL Job. In fact my Application is logging every detail and placing all details as I am logging many things and its priority based logging means logs depending upon the Environment. But just asking, is it good Idea to write my own Application or did I do wrong? My lead wanted to do it this way because there are many SSIS packages and because the SQL jobs they are running sometimes same time and creating lot of mess. But my application does it synchronously and it combines this synchronous process with another Asynchronous process of FileSystemWatcher, which keeps a record into the Database when file is dropped and then my App would take those details of path etc sets the connections and variables then calls the SSIS packages Synchronously and kills the execution of SSIS package if its taking too long. All these features are implemented by using C# code, if anybody has better advise please let me know their opinions. Just want to calculate pros and cons from some other developers just to check my process, in fact I believe all Programmers are always learners :).
Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."
-
Hi, I have and SSIS Package, my lead wants me to create a C# application that sets Variables, Connections and everything properly and executes the package, I did that, I even have written OnError event and logged the Error why SSIS failed to execute. As far I saw there is no difference between my Application and SQL Job. In fact my Application is logging every detail and placing all details as I am logging many things and its priority based logging means logs depending upon the Environment. But just asking, is it good Idea to write my own Application or did I do wrong? My lead wanted to do it this way because there are many SSIS packages and because the SQL jobs they are running sometimes same time and creating lot of mess. But my application does it synchronously and it combines this synchronous process with another Asynchronous process of FileSystemWatcher, which keeps a record into the Database when file is dropped and then my App would take those details of path etc sets the connections and variables then calls the SSIS packages Synchronously and kills the execution of SSIS package if its taking too long. All these features are implemented by using C# code, if anybody has better advise please let me know their opinions. Just want to calculate pros and cons from some other developers just to check my process, in fact I believe all Programmers are always learners :).
Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."
Using C# to kick off SSIS jobs is just fine. I've done it too and it works great. It sounds like you built a good system. :thumbsup:
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
-
Using C# to kick off SSIS jobs is just fine. I've done it too and it works great. It sounds like you built a good system. :thumbsup:
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
-
Hi, I have and SSIS Package, my lead wants me to create a C# application that sets Variables, Connections and everything properly and executes the package, I did that, I even have written OnError event and logged the Error why SSIS failed to execute. As far I saw there is no difference between my Application and SQL Job. In fact my Application is logging every detail and placing all details as I am logging many things and its priority based logging means logs depending upon the Environment. But just asking, is it good Idea to write my own Application or did I do wrong? My lead wanted to do it this way because there are many SSIS packages and because the SQL jobs they are running sometimes same time and creating lot of mess. But my application does it synchronously and it combines this synchronous process with another Asynchronous process of FileSystemWatcher, which keeps a record into the Database when file is dropped and then my App would take those details of path etc sets the connections and variables then calls the SSIS packages Synchronously and kills the execution of SSIS package if its taking too long. All these features are implemented by using C# code, if anybody has better advise please let me know their opinions. Just want to calculate pros and cons from some other developers just to check my process, in fact I believe all Programmers are always learners :).
Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."
Yeah, I've worked on systems where we built C# (and dare I say it, VB6) apps to monitor, trigger, kill SSIS packages. To be fair most of them began their existence before MS introduced all of the help that is now available with SQL Jobs... but the extra level of *specific* logging far outweighed the "out of the box" solution. When you are in a situation where there are many packages / jobs/ etc sometimes that extra level of customisation can pay for itself
-
Yeah, I've worked on systems where we built C# (and dare I say it, VB6) apps to monitor, trigger, kill SSIS packages. To be fair most of them began their existence before MS introduced all of the help that is now available with SQL Jobs... but the extra level of *specific* logging far outweighed the "out of the box" solution. When you are in a situation where there are many packages / jobs/ etc sometimes that extra level of customisation can pay for itself
Thanks my friend, yeah logging was needed I just want to know what's going on inside of its execution, but its priority based though that, in Dev it sets to lowest priority but in Prod it writes only Exceptions and Failures only.
Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."
