If you want to run them in order, don't run them ASYNC! On Wed, Mar 2, 2011 at 1:57 PM, littleccguy <[email protected]>wrote:
> C# 3.5 VS 2008 > SQL 2008 > Win XP > > Still learning, be gental. > > Some one has asked me to create a little exe that will run a series of > stored procedures sequentially. Each are dependant on the one before > it completing successfully, else show which failed and error and > break. > > I asked him why doesn't he do this with SSIS. He said dev does not > want any jobs set up on the test server that wouldn't be used on a > production server. - fine. > > I have tried working through this using async communication. Most of > what I have comes from here: > http://msdn.microsoft.com/en-us/library/7b6f9k7k(v=VS.90).aspx > > However, there is no user interaction required because some of the job > run long. He just wants to start the exe and walk away. > > Maybe I shouldn't be using async. I'm just not sure. Here is what I > would like: > Running sp1... > sp1 completed successfully > Running sp2... > sp2 completed successfully > > With async I end up with > Running sp1... > Running sp2... > sp1 completed successfully > sp2 completed successfully > > Any simple ideas or examples you can point me too would be great. > > Thanks >
