Hi,
Can anyone tell me why localized MSDEs are necessary? Does
it have anything to do with storing localized strings?
Would the English version of an MSDE instance installed on
a - let's say - Chinese version of Windows OS, have
problems storing and working with Chinese characters?
hi Lee,
"Lee" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:19cdd01c4225d$c8ee9b80$a601280a@.phx.gbl...
> Hi,
> Can anyone tell me why localized MSDEs are necessary? Does
> it have anything to do with storing localized strings?
> Would the English version of an MSDE instance installed on
> a - let's say - Chinese version of Windows OS, have
> problems storing and working with Chinese characters?
nope... Localized versions have nothing to do with data storage...
Localized versions are only versions with localized strings contained in the
localized resource libraries...
All localized versions can store unicode data and set sort order and
collations as needed...
further info about collation can be found starting at
http://msdn.microsoft.com/library/de...ar_da_1pwz.asp
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you very much for your answer.
Lee
>--Original Message--
>hi Lee,
>"Lee" <anonymous@.discussions.microsoft.com> ha scritto
nel messaggio[vbcol=seagreen]
>news:19cdd01c4225d$c8ee9b80$a601280a@.phx.gbl...
Does[vbcol=seagreen]
on
>nope... Localized versions have nothing to do with data
storage...
>Localized versions are only versions with localized
strings contained in the
>localized resource libraries...
>All localized versions can store unicode data and set
sort order and
>collations as needed...
>further info about collation can be found starting at
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/architec/8_ar_da_1pwz.asp
>hth
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
Showing posts with label localized. Show all posts
Showing posts with label localized. Show all posts
Monday, March 12, 2012
localized messages for SQL SERVER 2000
I found a usefull link to my problem : http://support.microsoft.com/Default.aspx?id=277535
But I am unable to find the s80xLang.exe file anywhere. I have looked through all my DVDs and nothing.
Anyone know where to look or download it from ?
The KB article mentions that you need to contact Customer Support to be able to download this. That wording implies the file is not available for public download. If you use email support to open a case with CSS, I'm pretty sure they will either send the file to you or provide you with the path to the download.|||All the developper email contacts costs money for support. I called support and they gave me the same response : I need to give a credit card to the routing agent and the support tech will decide if it's free or not after we resolve the issue. I have sent an email through our partner account and am waiting for a response.
I noticed that a lot of people are looking for an answer on this topic.
|||Anyone has had success in obtaining the localization s80xLang.exe file?
What's the point of Microsoft for not making this file public (or better, include it on the original product CD)?
|||Hi Antonio,
I finally called microsoft with our partner ID because we have so many free calls per year we can use. After speaking to a SQL specialist, he sent me the file. They were supposed to make the file public on the web site (it's available for them internally) but not for the rest of us.
You can give them a call and they will send you the file. I was not charged for the support call since it's their mistake.
Good luck and take care
|||All right, I've got the localization file (thanks, Marco!).... only to discover that it doesn't work with SQLServer 2005!
The problem is:
1 - for the script to run it must have permission to update the system table sysmessage;
2 - up to SQL 2000 this was achieved by issuing "sp_configure 'allow updates',1" or starting SQL with the -m option;
3 - SQL 2005 explicity states that updates to system tables are not allowed and that "sp-configure allow updates" is outdated and won't work (http://msdn2.microsoft.com/en-us/library/ms144262.aspx). Running the script in single-user mode (starting SQL with the -m option) doesn't work either, since "updates to system tables are not allowed".
Any ideas or further help will be appreciated.
Regards,
Antonio Plais - Brazil
|||Further developments on localizing SQL 2005 messages:
1 - I'm developing an application using SQL Express 2005, and I'd like to show SQL messages in Brazilian Portuguese (one of the SQL 2005 supported languages);
2 - The solution pointed by Microsoft support doesn't work on SQL 2005;
3 - Localized Brazilian SQL Express 2005 Standard can be downloaded from Microsoft, while SQL Express 2005 Advanced is available only in English;
4 - Standard edition doesn't install full-text search; trying to install it from Advanced edition (after installing the Brazilian standard version) doesn't work;
5 - So, until Microsoft gently makes available a Brazilian Advanced version, I'll have to choose between localized messages or full-text search;
How hard Microsoft can make our lives!
Regards,
Antonio Plais - Brazil
localized messages for SQL SERVER 2000
I found a usefull link to my problem : http://support.microsoft.com/Default.aspx?id=277535
But I am unable to find the s80xLang.exe file anywhere. I have looked through all my DVDs and nothing.
Anyone know where to look or download it from ?
The KB article mentions that you need to contact Customer Support to be able to download this. That wording implies the file is not available for public download. If you use email support to open a case with CSS, I'm pretty sure they will either send the file to you or provide you with the path to the download.|||All the developper email contacts costs money for support. I called support and they gave me the same response : I need to give a credit card to the routing agent and the support tech will decide if it's free or not after we resolve the issue. I have sent an email through our partner account and am waiting for a response.
I noticed that a lot of people are looking for an answer on this topic.
|||Anyone has had success in obtaining the localization s80xLang.exe file?
What's the point of Microsoft for not making this file public (or better, include it on the original product CD)?
|||Hi Antonio,
I finally called microsoft with our partner ID because we have so many free calls per year we can use. After speaking to a SQL specialist, he sent me the file. They were supposed to make the file public on the web site (it's available for them internally) but not for the rest of us.
You can give them a call and they will send you the file. I was not charged for the support call since it's their mistake.
Good luck and take care
|||All right, I've got the localization file (thanks, Marco!).... only to discover that it doesn't work with SQLServer 2005!
The problem is:
1 - for the script to run it must have permission to update the system table sysmessage;
2 - up to SQL 2000 this was achieved by issuing "sp_configure 'allow updates',1" or starting SQL with the -m option;
3 - SQL 2005 explicity states that updates to system tables are not allowed and that "sp-configure allow updates" is outdated and won't work (http://msdn2.microsoft.com/en-us/library/ms144262.aspx). Running the script in single-user mode (starting SQL with the -m option) doesn't work either, since "updates to system tables are not allowed".
Any ideas or further help will be appreciated.
Regards,
Antonio Plais - Brazil
|||Further developments on localizing SQL 2005 messages:
1 - I'm developing an application using SQL Express 2005, and I'd like to show SQL messages in Brazilian Portuguese (one of the SQL 2005 supported languages);
2 - The solution pointed by Microsoft support doesn't work on SQL 2005;
3 - Localized Brazilian SQL Express 2005 Standard can be downloaded from Microsoft, while SQL Express 2005 Advanced is available only in English;
4 - Standard edition doesn't install full-text search; trying to install it from Advanced edition (after installing the Brazilian standard version) doesn't work;
5 - So, until Microsoft gently makes available a Brazilian Advanced version, I'll have to choose between localized messages or full-text search;
How hard Microsoft can make our lives!
Regards,
Antonio Plais - Brazil
Localization issue
Hi All,
I already have a web site running with SQL Server as a backend (in
english)For future growth, I would like to make it localized. Regarding
the database, I have come up with several approaches.
1) just simply add the column in those table which needs different
language.
2) add additional tables to do it.
3) create a new database to store different language's information
As mentioned, my database have already been implemented, so the minimum
modification is preferred. Could you guys suggest me the best way to do
it?
Another thing, if I alter my existing database into UTF-8 now, will it
affect the original data (ie. English).
Thanks.
Iceiceriver (hfung@.hotmail.com) writes:
> I already have a web site running with SQL Server as a backend (in
> english)For future growth, I would like to make it localized. Regarding
> the database, I have come up with several approaches.
> 1) just simply add the column in those table which needs different
> language.
> 2) add additional tables to do it.
> 3) create a new database to store different language's information
> As mentioned, my database have already been implemented, so the minimum
> modification is preferred. Could you guys suggest me the best way to do
> it?
Adding multi-language support is a task with an impact. Without knowing
the nature of your database it is hard to give recommendations.
In the system I work with, we once faced this problem. At that time,
many our tables had two name columns, for instance countryname and
countrynamefor, holding the Swedish and English name respectively. As
we entered the Finnish market, we needed support for a third language,
since in Finland, both Swedish and Finnish are official languages.
After some discussion, we decided to take the big step: the names were
moved out specific name tables. For instance the countries table
would get a subtable countrynames with the key (countrycode, languageid).
For simplicity we did keep a name column in the main table, so we
can use that as a fall back if there is no name in the current language
in the name table.
Adding an extra column may be easy for the first language you support,
but if you add specific tables, you have the infrastructre built for
your third, fourth language etc.
> Another thing, if I alter my existing database into UTF-8 now, will it
> affect the original data (ie. English).
There is no support for storing data in SQL Server as UTF-8. To store
Unicode data, use UCS-2. (The same as UTF-16, but SQL 2000 does not
support surrogates.) That is the nchar/nvarchar datatypes. Note that
depending on which languages you plan to support, you can still make it with
char/varchar.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland,
Thanks for your reply. I am wondering if there is any sample DB schema
available on the web. I would like to see an example that how several
related-tables also need to be localized. Any suggestion to re-arrange
those existing relationship? I am kinda new to localization problem,
please give me some hints.
"After some discussion, we decided to take the big step: the names were
moved out specific name tables. For instance the countries table
would get a subtable countrynames with the key (countrycode,
languageid).
For simplicity we did keep a name column in the main table, so we
can use that as a fall back if there is no name in the current language
in the name table."
Erland Sommarskog wrote:
> iceriver (hfung@.hotmail.com) writes:
> > I already have a web site running with SQL Server as a backend (in
> > english)For future growth, I would like to make it localized.
Regarding
> > the database, I have come up with several approaches.
> > 1) just simply add the column in those table which needs different
> > language.
> > 2) add additional tables to do it.
> > 3) create a new database to store different language's information
> > As mentioned, my database have already been implemented, so the
minimum
> > modification is preferred. Could you guys suggest me the best way
to do
> > it?
> Adding multi-language support is a task with an impact. Without
knowing
> the nature of your database it is hard to give recommendations.
> In the system I work with, we once faced this problem. At that time,
> many our tables had two name columns, for instance countryname and
> countrynamefor, holding the Swedish and English name respectively. As
> we entered the Finnish market, we needed support for a third
language,
> since in Finland, both Swedish and Finnish are official languages.
> After some discussion, we decided to take the big step: the names
were
> moved out specific name tables. For instance the countries table
> would get a subtable countrynames with the key (countrycode,
languageid).
> For simplicity we did keep a name column in the main table, so we
> can use that as a fall back if there is no name in the current
language
> in the name table.
> Adding an extra column may be easy for the first language you
support,
> but if you add specific tables, you have the infrastructre built for
> your third, fourth language etc.
> > Another thing, if I alter my existing database into UTF-8 now, will
it
> > affect the original data (ie. English).
> There is no support for storing data in SQL Server as UTF-8. To store
> Unicode data, use UCS-2. (The same as UTF-16, but SQL 2000 does not
> support surrogates.) That is the nchar/nvarchar datatypes. Note that
> depending on which languages you plan to support, you can still make
it with
> char/varchar.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||iceriver wrote:
> Erland,
> Thanks for your reply. I am wondering if there is any sample DB
schema
> available on the web. I would like to see an example that how several
> related-tables also need to be localized. Any suggestion to
re-arrange
> those existing relationship? I am kinda new to localization problem,
> please give me some hints.
Why change the database, other than just for the different language?
I'd suggest that keeping table and field names in the original language
would be simplest.
It's the user interface really needs to have local name of fields and
(perhaps) localised error messages.
How you'd do this best depends on what the user interface is
specifically written in.
One method...
Stick these in an xml file distributed with the app or a table in the
database with a structure something like
Language,
Message_No,
Message
Use something in the app to specify the language your user has and look
up the entry in the message field for each text box/error.
Potentially a fair bit of work. The last app I wrote is multi-national
but the company's standard language for computer systems is english for
this reason.
You also have to remember to handle different formatting of dates,
numbers ( comma or full stop as decimal place ).|||iceriver (hfung@.hotmail.com) writes:
> Thanks for your reply. I am wondering if there is any sample DB schema
> available on the web. I would like to see an example that how several
> related-tables also need to be localized. Any suggestion to re-arrange
> those existing relationship? I am kinda new to localization problem,
> please give me some hints.
I have no idea what is out there. But I have a strong feeling that the
answer depends on your business, and you are asking me question about a
database I don't know anything about. What was the right answer for us
may not be for you.
But there is one thing I forgot to mention in my prevoius reply: the
database is the easy part. The hard and expensive work is all the
translation. With a good architecture, you can easily add an other
language from a technical point of view. But the translation work will
be the same each time. And the maintenance of all languages will increase
for each new language you add.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Andy: Thanks, I also heard about the XML stuff may help, but I don't
know too much details in it.
Erland: Thanks, how a architecture and language addition will increase
the maintenance load?
If you guys encounter any good book/web reference regarding the
localization issue, please feel free to let me know. Thanks so much.|||Andy: Thanks, I also heard about the XML stuff may help, but I don't
know too much details in it.
Erland: Thanks, how a architecture and language addition will increase
the maintenance load?
If you guys encounter any good book/web reference regarding the
localization issue, please feel free to let me know. Thanks so much.|||iceriver (hfung@.hotmail.com) writes:
> Erland: Thanks, how a architecture and language addition will increase
> the maintenance load?
You don't localize once. As you change your site, you will have localize
all those changes as well.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Subscribe to:
Posts (Atom)