When we load a large PO with Dftl PO Lines set to All, the screen will show "Unresponsive" and the user will wait 30+ seconds before the PO Lines are successfully loaded. I ran a SQL Trace and found the "Fetch API_Cursor" and "sp_cursorfetch" duration to be the only events with excessive durations(509) , reads(47620), and CPU(484). I also noted that it appears to call these events for each line item on the PO.
Since performance is very good in general, I am not concerned that this is related to our SQL Server performance. I suspect the screen needs some performance tweeking. Any suggestions for improving the performance in this screen would be appreciated.
SL 2011 Version 8.00.20321.00
*This post is locked for comments