I have a client application that flushes data to the source table. This client application performs an asynchronous call to a stored procedure that actually parses raw data in tables. This processing is processed by the stored procedure. This stored procedure can take up to an hour and a half. We want the client application to call the stored proc to exit and stop working completely. As soon as we kill the client application that invokes the stored process, completion of the stored procedure.
What is the best way to achieve this? I do not want to start work on the server. I want the client application to start this processing. The database trigger (my first idea) does not solve the problem either because it does not account for the insert until the stored procedure called by the trigger is completed.
Here is the Async method. I am using LINQ. Can I somehow change this? Or do I need a new design?
partial class MetaDataContext
{
delegate int Process_CompleteCycle2Delegate(int? frequencyID, int? cycleID);
public void Process_CompleteCycle2Async(int? frequencyID, int? cycleID)
{
Process_CompleteCycle2Delegate completeCycleDelegate = new Process_CompleteCycle2Delegate(this.Process_CompleteCycle2);
IAsyncResult async = completeCycleDelegate.BeginInvoke(frequencyID, cycleID, null, null);
}
source
share