Well, I just googled and went all over to find out what are the ways of getting out of this problem. I just found that too many people have gone thru this before and there are just too many articles on utf-8 vs utf16, encoding of dbs, etc etc..including pages and pages of scripts to run to alter the collations etc.
Finally, as usual after a tiring search of answer to this issue - I found what is the real problem. The problem is this: I had made the database in India with the default collation sequence that comes with sql server express 2005. Language used in English.
Now the database has gone to another country where the language is Arabic and the Regional Language Setting is Jordan(Arabic). Now when the SQL Express is installed in that country it has selected a collation sequence (probably) based on the collation sequence and is reading the exisiting userid and password data of my database file based on that collation sequence.
Now how to solve this issue: Solutions given are:
a) Rejig the data to the new coll.seq..using scripts, tools etc..The sql scripts given there are just complex enough and none can guarantee they will solve the issue fully..hence you need to try.
b) Recreate the database to what ever the collation sequence is there by using create table procedures and then move the data. This seems to be a most preferred soltuion by many as they say it does the job quicker. My app has a few XML and XL backup and reload features and this is what I am choosing..
Can anyone comment on this pl or suggest a better one which is quicker ?
Thanks.