Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 2720

Re: Stored procedure waiting too long to start executing

$
0
0

Mark,

 

First, thanks for taking time to answer this so elaborately! Here are the answers for each of the above sections.

 

optimization timeout limit (default 10)

sproc optimize timeout limit (default 40)

 

     Both these parameters are at the default values. Also, the 'optimizer level' is set to ase_current. The compatibility mode is NOT enabled.

 

     BTW, how does the ASE compute the *estimated* execution time for a stored procedure/query?

 

optimization goal

 

     In both ASE 15.0.3 and ASE 15.7 the optimizer goal is set to allrows_dss. I will repeat the experiment with allrows_oltp on Monday. Using the allrows_oltp for experimentation is fine but setting it at the server level is like taking a few steps backwards, IMHO.

 

process vs threaded kernel mode

 

     We will leave this for a later discussion as the last option.

 

simplification of queries

 

     Almost all attributes in our tables are based on User Defined Datatypes. However, some variables declared in the stored procedure do not use the UDDs and instead use the basic datatypes. I will look more deeply for any datatype mismatches.

 

Bret: I am anxious to know your findings from the stacktraces.

 

Thanks,

Anil


Viewing all articles
Browse latest Browse all 2720

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>