"Z Fields" in Linked Info Areas

This problem can be identified by a quite high number of follow-up requests applied to other info areas (with conditions applied to ID) following the initial SQL statement in the synchronization request:

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 [...]

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:37; 15;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45];<READ=FI; Cur=0; SID=07AF61D0; ' ,0,0';

2012.10.30;13:50:37; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; SELECT [...] WHERE ID=?

2012.10.30 ;13:50:37 ; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; V1='429496729665';

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

;SID [nqgpay55rl3iil45lagq1l45];<READ=KP; Cur=0; SID=07AF61D0; ' ,0,0';

2012.10.30;13:50:37; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; SELECT […] WHERE ID=?

2012.10.30 ;13:50:37 ; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; V1='429496730029';

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

2012.10.30 ;13:50:37 ; 0;update.net.core.Sql ;Notice ;SID[nqgpay55rl3iil45lagq1l45];timer=0; Ok; 0ms; SID=07AF61D0;>

2012.10.30;13:50:37; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45];<READ=FI; Cur=0; SID=07AF61D0; ' ,0,0';

2012.10.30;13:50:37; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; SELECT […] WHERE ID=?

2012.10.30 ;13:50:37 ; 0;update.net.core.Sql ;Info ;SID[nqgpay55rl3iil45lagq1l45]; V1='4294967308';

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

You can avoid this problem by using the corresponding link fields in the configuration instead of the Z fields, i.e. the fields for the first name and last name from the KP info area instead of the "Person" Z field. These fields must subsequently be synchronized with the KP dataset.

This issue depends on the number of synchronized records. Reduce the offline dataset in order to execute a smaller number of additional statements.