The Statement Returns too Much Data

The problem can be identified by the statement executing successfully but returning a very large amount of data - this is the case if the statement completes executing (i.e. a runtime and results set are specified) and is followed by several RPACK lines for the info area being synchronized.

2012.10.30 ;13:50:36 ; 16;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45];< RPACK =MA; Cur=1; SID=07AF61D0;

2012.10.30;13:50:36; 15;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; SELECT [...] FROM BTB70_MA […]

2012.10.30 ;13:50:37 ; 765;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; EXEC=765; Conn=2; Cur=1; Rec=1024; Ret=0; Res=1024;

2012.10.30 ;13:50:40 ; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45];< RPACK =MA; Cur=1; SID=07AF61D0;

2012.10.30 ;13:50:40 ; 16;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; EXEC=16; Conn=2; Cmd=FNEXT; Cur=1; Rec=1024; Ret=0; Res=1024;

2012.10.30 ;13:50:40 ; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45];< RPACK =MA; Cur=1; SID=07AF61D0;

2012.10.30 ;13:50:40 ; 16;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; EXEC=16; Conn=2; Cmd=FNEXT; Cur=1; Rec=1024; Ret=0; Res=1024;

[...]

This problem can also cause CRM.pad to "crash" (it is terminated by the iOS operating system because the response cannot be processed due to a lack of memory resources). This occurrence depends on a record's width (the number of fields and their length) and on the number of records (usually more than 50,000 records) in one info area synchronized on the device. Try to reduce the data volume that is synchronized to improve the performance of the client.