Hi,

yes so it seems...

The difference is that in my case the insert goes through Informatica ETL tool. There is something with the Unix ODBC API or in the tool itself that causes this. I know I must try to investigate that.

But since 0xB54E921E9BF81A19E76D8D15D16AD000 and 0xB54E921E9BF81A19E76D8D15D16AD0 are the same value atleast when comparing in Where clause

select 'Hello' where 0xB54E921E9BF81A19E76D8D15D16AD000 = 0xB54E921E9BF81A19E76D8D15D16AD0 ==> 'Hello'
but
select 'Hello' where 0xB54E921E9BF81A19E76D8D15D16AD0000 = 0xB54E921E9BF81A19E76D8D15D16AD0 ==> Nothing
and then again
select 'Hello' where 0xB54E921E9BF81A19E76D8D15D16AD00000 = 0xB54E921E9BF81A19E76D8D15D16AD0 ==> 'Hello'

So a even number of trailing zeroes does not change the value.

Suppose I don't find any explanation/reason from Informatica, is there anything I can do with T-SQL?

Ville