Viewing 6 posts - 1 through 7 (of 7 total)
Seems like I found a solution and I'm pretty sure that the [DelimitedSplitN4K] was the cause of the problem (the catch all query might be a problem later when number...
April 8, 2016 at 8:59 am
I've tried all suggested solutions in the mentioned article - but they dosn't seem to have any huge effect on my problem.
tblCase contains 6043 rows and tblCaseOrderLine contains 12589 -...
April 8, 2016 at 5:24 am
I actually read the article, and have also added the OPTION recompile to the procedure - but I don't think it has any effect on the performance. The entire procedure...
April 7, 2016 at 7:05 am
Because of the Join with tblCaseOrderLines has been removed, I had to rewrite below AND-clause (was left out of the example for simplicity). DelimitedSplitN4K is a Table Valued function that...
April 7, 2016 at 6:41 am
Thanks for the suggestions. I've now implemented it, the way you described and it works very well.
April 7, 2016 at 5:45 am
Yes, you're right: CaseOrderLine (and other tables) are only used for filtering since loading of the entire case (including orderlines) is handled in code in the middle layer.
I'll try your...
April 4, 2016 at 3:56 am
Viewing 6 posts - 1 through 7 (of 7 total)