UshaD

 Profile Answers by UshaD 

• Feb 13th, 2008

 

When a SQL is run, there is a lock on the table by the database until that section is completed. If during that time there runs some other process which will use the same table locked by our section using call section, this process will fail.

Alekhya

• Aug 2nd, 2011

 

SQL and Call Section are Mutually exclusive Actions ,We can't use both at same step.

Example:

The Step1 having 'SQL' action.Suppose if you use callsection action in the step1 it calls the another 'Section2',the Section2 contains the 'step2' and step contains 'Actions' in this step2 have 'SQL' Action .

At this situations system didn't find to process the 'SQL' Actions means which 'SQL' action goes to first for processing. Thats why deadlock will occur if we use 'SQL' and 'Call Section' in the same Step.

bundi

• Mar 22nd, 2012

 

If the same step having Sql and Call Section which will effect the same table deadlock occurs so only they are mutually exclusive.

Vipin Jain

• Apr 12th, 2016

 

In case of SQL action, you can update any data.
Lets say a row is modified by the SQL action and now a new section is called from this steps call section.
Till this step completes data in the record will not be commited and a lock is there and prevents it to be updated again.
Now if there is a step in the called section where SQL action is updating the same row it will wait till the previous changes are committed. And these changes will not commit until the call section is completed...
Which makes a deadlock condition and process will remain in processing till the end of server life. ;P

Raj

• Sep 6th, 2017

 

It will never get dead lock.