Not Equals performance [duplicate]

Question

This question already has answers here:

Should I use != or <> for not equal in T-SQL? (13 answers)

Closed 8 years ago.

Is there a difference in performance between != and <>?

Bonus: why do people get upset when I use != instead of <>? I am of course speculating that all programmers get upset about this, however I have worked for two companies now that "require" the use of <>

Answer 1

Short answer: no, there's no difference in performance.

As for the bonus question, I imagine people get upset because != is not defined in the SQL 92 standard and is therefore less likely to be portable.

Edit

The SQL 92 standard can be found here and defines the not equals operator as follows:

<not equals operator> ::= <>

Answer 2

They do not have performance differences, it's certainly for matters of standards/consistence. Take a look at this question: Should I use != or <> for not equal in TSQL?