Home Forums SQL Server 7,2000 T-SQL Use of N with unicode constant parameter RE: Use of N with unicode constant parameter

  • Thank you for the reply - I sure like SQL Central - lots of good info.

    It is good for us all to state and understand that join fields need to be of same type.

    However, my central question - very specifically - when/why is the N needed.

    Specifically in a database upgrade from varchar to nvarchar.

    If 250 out of 2500 SPs contain constant value parameters being set in queries...

    Do all those SPs and statements now need change - with an N in front of the constant?

    I hypothesize that the N ONLY MATTERS when the constant's value is outside the database collation.

    I am not changing the collation.

    I do not think all those SP lines need changing.

    Thoughts?