The usual way to find such discrepancies is to apply recno() and rowno() to all loads and then to count and to compare all the records and of course to look which records are missing - often it's then quite obvious why they are missing. Before going this way it might be helpful to repeat both approaches several times to check if the number of records is always the same or if the change randomly because of any locking of records.
Beside this there are multiple causes possible why both approaches differ, for example if any of these loads contain a DISTINCT statement. Another point are the values itself - if the join keys are pure numeric and the used number-system of your database and this from Qlik is different (it's quite probably the case) and/or if the keys contain some kind of NULL - which may be changed unnoticed in Qlik by using any NULL variables or NULL mappings - and which also may handled differently between the tools. Also the used driver may change the key-values and/or the number of records of any of these tables.
- Marcus
I assume that the type of data associated with the T1.ITEM and T2.ITEM fields is varchar. Based on this I suggest you try the following...
Lower(T1.ITENOM) AS Itenom
Lower(T2.ITENOM) AS Itenom
Tried that as well...my master tables i have given it as text(ITNO), i give the right format while loading the data itself so that i wont get such errors.
The usual way to find such discrepancies is to apply recno() and rowno() to all loads and then to count and to compare all the records and of course to look which records are missing - often it's then quite obvious why they are missing. Before going this way it might be helpful to repeat both approaches several times to check if the number of records is always the same or if the change randomly because of any locking of records.
Beside this there are multiple causes possible why both approaches differ, for example if any of these loads contain a DISTINCT statement. Another point are the values itself - if the join keys are pure numeric and the used number-system of your database and this from Qlik is different (it's quite probably the case) and/or if the keys contain some kind of NULL - which may be changed unnoticed in Qlik by using any NULL variables or NULL mappings - and which also may handled differently between the tools. Also the used driver may change the key-values and/or the number of records of any of these tables.
- Marcus
Vinayak, did Marcus' follow-up post help you get things sorted? If so, be sure to give him credit by using Accept as Solution, but you can also post what you found using his suggestion and mark that post too, as I think in this case both would be needed, this way folks will know it helped you and if you can state what the actual issue was, they will have that piece too. If you are still working on things, shout back with an update.
Regards,
Brett