|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Hebrew Sql 2000 to 2005 Collation Problem ?Dear Gurus :
i have a database on sql 2000 server with default Collation set to ( British English ) and the databse have hebrew character inside and everything works great now that microsoft comes with the new sql we deatach the database from 2000 and attached it to 2005 version , now the problem is : we have qestion mark instead of the hebrew character, despite that the 2005 server has identical Collation configuration we still get ???????? ( qestion marks) instead of getting the hebrew character. can soomeone please please help me with this annoying problem . i approciate your help by advanced Hi
I assume this is an NTEXT field, if you check the UNICODE value for these characters with the UNICODE function you will check that the value is correct and it is a display issue. Check to see if other application will display these characters John Show quote "D.R" <D*@discussions.microsoft.com> wrote in message news:54E2FCD1-F975-4E96-9C3C-477DA37FD01D@microsoft.com... > Dear Gurus : > i have a database on sql 2000 server with default Collation set to ( > British > English ) and the databse have hebrew character inside and everything > works > great now that microsoft comes with the new sql we deatach the database > from > 2000 and attached it to 2005 version , now the problem is : we have > qestion > mark instead of the hebrew character, despite that the 2005 server has > identical Collation configuration we still get ???????? ( qestion marks) > instead of getting the hebrew character. can soomeone please please help > me > with this annoying problem . > > i approciate your help by advanced Dear Jhon :
first thanks allot for your help , i think i didn't understand what is the solution you referring to , can you please be more specific , cause we can't change the application >? Show quote "John Bell" wrote: > Hi > > I assume this is an NTEXT field, if you check the UNICODE value for these > characters with the UNICODE function you will check that the value is > correct and it is a display issue. > > Check to see if other application will display these characters > > John > "D.R" <D*@discussions.microsoft.com> wrote in message > news:54E2FCD1-F975-4E96-9C3C-477DA37FD01D@microsoft.com... > > Dear Gurus : > > i have a database on sql 2000 server with default Collation set to ( > > British > > English ) and the databse have hebrew character inside and everything > > works > > great now that microsoft comes with the new sql we deatach the database > > from > > 2000 and attached it to 2005 version , now the problem is : we have > > qestion > > mark instead of the hebrew character, despite that the 2005 server has > > identical Collation configuration we still get ???????? ( qestion marks) > > instead of getting the hebrew character. can soomeone please please help > > me > > with this annoying problem . > > > > i approciate your help by advanced > > > Hi
I would assume that your Hebrew text is in a unicode datatype column, which should not have changed at all, this can be verified by find what the value the unicode function returns for these characters; therefore it would be the application that can not display it. '?' is usually used for a value that is not understood. Check locales etc on the client and other programs that you would expect to display these characters. John Show quote "D.R" <D*@discussions.microsoft.com> wrote in message news:C2053250-1397-4954-B9A1-E7915D71E0D4@microsoft.com... > Dear Jhon : > first thanks allot for your help , i think i didn't understand what is the > solution you referring to , can you please be more specific , cause we > can't > change the application >? > > "John Bell" wrote: > >> Hi >> >> I assume this is an NTEXT field, if you check the UNICODE value for these >> characters with the UNICODE function you will check that the value is >> correct and it is a display issue. >> >> Check to see if other application will display these characters >> >> John >> "D.R" <D*@discussions.microsoft.com> wrote in message >> news:54E2FCD1-F975-4E96-9C3C-477DA37FD01D@microsoft.com... >> > Dear Gurus : >> > i have a database on sql 2000 server with default Collation set to ( >> > British >> > English ) and the databse have hebrew character inside and everything >> > works >> > great now that microsoft comes with the new sql we deatach the database >> > from >> > 2000 and attached it to 2005 version , now the problem is : we have >> > qestion >> > mark instead of the hebrew character, despite that the 2005 server has >> > identical Collation configuration we still get ???????? ( qestion >> > marks) >> > instead of getting the hebrew character. can soomeone please please >> > help >> > me >> > with this annoying problem . >> > >> > i approciate your help by advanced >> >> >> D.R (D*@discussions.microsoft.com) writes:
> i have a database on sql 2000 server with default Collation set to ( Exactly where does these ? appear? That is, is in your application, or> British English ) and the databse have hebrew character inside and > everything works great now that microsoft comes with the new sql we > deatach the database from 2000 and attached it to 2005 version , now the > problem is : we have qestion mark instead of the hebrew character, > despite that the 2005 server has identical Collation configuration we > still get ???????? ( qestion marks) instead of getting the hebrew > character. can soomeone please please help me with this annoying problem > . where are you looking? Also, which data type is the column? -- Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx  |
|||||||||||||||||||||||
Other interesting topics