I noticed, through a Profiler session, that AX makes extensive use of server-side cursor statements, such as
exec sp_cursorexecute 4, @P1 output, @P2 output, @P3 output, @P4 output, 2, 1
What can I do to change this behavior? Server-side cursors are resource hogs and not the most efficient method of using data sets:
SIGH. Maybe in version 5…