MSSQL vor and wor is considered equals?
Posted on 2011-03-10
I have an update statement where i try to insert the text "vor" into a column called username. There is already a username = 'wor", and the system gives me a:
Violation of UNIQUE KEY constraint 'tc_usertbl_username'. Cannot insert duplicate key in object 'dbo.usertbl'.
as we all can see, wor is not like vor, but my sql server seems to think differently..
i have tried to change username to nvarchar, and it seems to work, but this is an old system, and i have no idea if anybody has done a "select * from usertbl" and referenced the position instead of column names. if so, the workaround i have done will make it fail.
i do not want to create a new table, move data, drop foreign keys, drop old, rename new, create new foreign keys, because i have no idea how many fk's there are..
does anybody have any easier way of getting around this problem?