Home
Analytics
Actuate SqlServer JDBC Driver returns Max nesting level exceeded, data request fails
jshaw
<p>I have created a DataSet that calls a stored procedure "ABC" in a SqlServer database, and within the sproc it calls a database function that is (in some cases) recursive. </p>
<p> </p>
<p>When ABC is run in SqlServer Mngmt Studio it works fine, but when run from the BIRT designer it returns "Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32)".</p>
<p> </p>
<p>So the question is clearly how do I stop the driver from being so strict in its application of this rule. Apparently my SSMS doesn't apply the same setting, but it would appear the JDBC driver does, either it doesn't like recursive calls at all, or it applies this 32 limit.</p>
<p> </p>
<p>My strong suspicion is that the initial settings of the driver do not allow recursion at all, since even when my function is doing no recursion the error is thrown. </p>
<p> </p>
<p>Any clues how to proceed?</p>
<p> </p>
Find more posts tagged with
Comments
JFreeman
<p>What version of BIRT are you using?<br>
What SQL Server JDBC driver are you using?</p>
<p> </p>
<p>My guess would be the same as your that the driver has a default limit that you are hitting.</p>
<p>We need to know more about the specific driver/version though.</p>