Re: Multilingual versions of SQL Express 2005 available ? Where ?



Thanks for the information;

I actually need to test the foreign languages as shipped in the sys.messages
view of the database for interpreting database errors properly in foreign
languages. I guess this part will have to be deferred until the foreign
languages ship.

We need to 'interpret' the error message returned in a SqlException so that
a proper message that makes sense to an end user can be conveyed.

The example I use is the SQL error message returned from the SQL server:
Violation of UNIQUE KEY constraint 'UQ__XYZ__234566''. Cannot insert
duplicate key in object 'dbo.TABLE'
(Error message number 2627)

needs to be interpreted and the user informed:

You cannot enter a duplicate 'code' for the 'xyz'.


The 'code' and 'xyz' part of the message has to be 'extracted' from the
constraint (UQ__XYZ...) stored in the database by
1) parsing the error message (in whatever language...) and extracting the
parameters from the error message (preserving what parameter number each is
based on the foreign language)
2) using the us_english version of the error message format (from
sys.messages), determine which parameter is the constraint name (in this case)
3) using the constraint name, retrieve from the database INFORMATION schema
the table and columns involved in the constraint violation
4) Map the information from 3 back through the DataBindings collection to
determine WHICH windows control on the user interface has the duplicate
information.
5) POST the error message to the appropriate control feedback provider so
the user is informed which control(s) have incorrect values.


Sound like fun ? :)

Would be easier if SqlExceptions had a better interface for at least
extracting the parameters supplied to the error message as numbered
parameters rather than us having to reverse format the actual error message
text (in foreign languages)

This discussion was made with Microsoft Advisory services over a year ago
and the above is the only solution we came up with.

"Steven Cheng[MSFT]" wrote:

> Hi Keith,
>
> As Mike has said, so far t here is no other language version of the SQL
> EXPRESS 2005 available. However, as for testing our own applicaiton's
> internationalization ability, it is not necessary to have a specific
> language version of SQL Express. All the english version SQL Server can
> store all the characters of other language.... Generally, if our
> application is using Unicode as the text's charset, the SQLserver's buildin
> unicode text column can correctly store them... Also, if you want to store
> the text as a specific charset(code page...), the SQLserver also provide
> most common Collations that mapped to those common charsets or codepages....
>
> There is a msdn article dicussing on the SQL 2000's international support,
> it also applies to all the sqlserver instances....
>
> #International Features in Microsoft SQL Server 2000
> Thanks,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> --------------------
> | From: "Mike Epprecht \(SQL MVP\)" <mike@xxxxxxxxxxxx>
> | References: <D9001CF8-0AEE-47ED-B98E-9C2CAE9D2E79@xxxxxxxxxxxxx>
> | Subject: Re: Multilingual versions of SQL Express 2005 available ? Where ?
> | Date: Wed, 14 Dec 2005 19:52:25 +0100
> | Lines: 29
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
> | X-RFC2646: Format=Flowed; Original
> | Message-ID: <eFWrF#NAGHA.1032@xxxxxxxxxxxxxxxxxxxx>
> | Newsgroups: microsoft.public.sqlserver.setup
> | NNTP-Posting-Host: 196.1.62.81.cust.bluewin.ch 81.62.1.196
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.setup:74037
> | X-Tomcat-NG: microsoft.public.sqlserver.setup
> |
> | Hi
> |
> | Non-English versions will be shipping early 2006.
> |
> | Regards
> | --------------------------------
> | Mike Epprecht, Microsoft SQL Server MVP
> | Zurich, Switzerland
> |
> | IM: mike@xxxxxxxxxxxx
> |
> | MVP Program: http://www.microsoft.com/mvp
> |
> | Blog: http://www.msmvps.com/epprecht/
> |
> | "Keith Dorken" <kadorken@xxxxxxxxxxxxx> wrote in message
> | news:D9001CF8-0AEE-47ED-B98E-9C2CAE9D2E79@xxxxxxxxxxxxxxxx
> | >I need to test multilingual support for our application in French
> (Canada)
> | > version of SQL Express 2005, but cannot find where (if) it is available?
> | >
> | > Thanks in advance for any pointers as to where the multlingual versions
> | > are
> | > hiding.
> | >
> | > Keith
> | >
> | >
> |
> |
> |
>
>
.



Relevant Pages

  • Re: Multilingual versions of SQL Express 2005 available ? Where ?
    ... you're using .net ADO.NE, since the ADO.NET will return the SQL error code, ... we may consider provide localized error message according to the error ... Microsoft Online Support ... | I actually need to test the foreign languages as shipped in the ...
    (microsoft.public.sqlserver.setup)
  • Re: Internationalizing pages
    ... > I'm writing a site in PHP with mySQL. ... > where $lang is a global variable containing locality string. ... I would use defines for each error message. ... Depending on what language is used, I would include that languages and use the ...
    (alt.php)
  • Re: Internationalizing pages
    ... > I'm writing a site in PHP with mySQL. ... > where $lang is a global variable containing locality string. ... I would use defines for each error message. ... Depending on what language is used, I would include that languages and use the ...
    (comp.lang.php)
  • Re: Problem installing SGI::FAM module
    ... Unfortunately FAM.pm doesn't manage well languages other thatn english. ... Edit FAM.pm, line 23 it searches for "Invalid" in a message, but if your ... error message contains. ...
    (comp.lang.perl.misc)
  • Re: Connecting to a sql server database
    ... You are trying to use integrated security in your app (as is shown in the ... line numbered code where the connection string is shown). ... sql server, hence integrated security fails. ... > causing the error message and what the correction for this. ...
    (microsoft.public.dotnet.general)

Loading