Alteryx Designer vs MS SQL Server aggregation differences [ Edited ]

[#1]

I am working on converting a data pipeline that runs on Alteryx Designer into a MS SQL Server query, and I am noticing that I get different results when I use the GROUP BY step. For example, both processes read from the same table that has 2,318,794 rows, but when I use aggregate functions (GROUP BY, MAX(), COUNT() and SUM()) they Alteryx process returns 2,089,738 rowsand the SQL query returns 2,089,238 (a 500 row difference) and the difference increases the more I aggregate, to the point that by the end of the process I end with a 60k lines difference between what  Alteryx returns and what my query returns.

Is there a difference on how Alteryx and MS SQL Server execute aggreation operations? Or how they handle NULL values when aggregating?

Any input or idea is appreciated, thank you.

[#2]

Is this for the NetMRI SQL database access?

[#3]

But one thing you must understand, is that SQL apply rules about some datatypes that can be different in other systems. I do not know what Alteryx Designer is, but, as an SQL expert and formerly a SQL Server MVP, I suspect this product to not conforms to the standard ISO SQL.

[#4]

I read your Question and i try to my best to complet you answer in the short explanation Handling of NULL values: Alteryx and MS SQL Server may handle NULL values differently during aggregations. In Alteryx, NULL values might be treated differently or excluded by default, while in SQL Server, they might be included in the calculations. This can lead to differences in the final result. Data types and precision: Check if there are any differences in data types or precision between the columns used in the aggregations. For example, if one system uses a floating-point data type and the other uses a decimal data type, there could be slight variations in the calculated results. Official site