I have a SQL Server 2000 application that must return raiserrors in multiple
languages. One of the languages is not in the list of supported languages
in master..syslanguages.
In SQL 6.5, there was a procedure sp_addlanguage that could be used to add
unsupported languages. This procedure is no longer available in SQL 2000.
The upgrade documentation suggests removing all references to sp_addlanguage
... as if to suggest that adding languages to SQL 2000 is not supported and
should not be done.
I could add the language directly to syslanguages (it works, I've tried it).
My question is: Is there actually a risk in adding a new language to
syslanguages? Are there any factors that I should be aware of?
Thanks,
BB
There may not be problem for the time being, but the structure of system
tables may change between versions of SQL Server, and selecting directly
from system tables is discouraged.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "bbofloma" <bbofloma@.online.nospam>
>Subject: Adding New Languages
>Date: Mon, 4 Apr 2005 15:55:03 -0400
>Lines: 20
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <e7$DLDVOFHA.3848@.TK2MSFTNGP14.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: d150-29-198.home.cgocable.net 24.150.29.198
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:51233
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I have a SQL Server 2000 application that must return raiserrors in
multiple
>languages. One of the languages is not in the list of supported languages
>in master..syslanguages.
>In SQL 6.5, there was a procedure sp_addlanguage that could be used to add
>unsupported languages. This procedure is no longer available in SQL 2000.
>The upgrade documentation suggests removing all references to
sp_addlanguage
>... as if to suggest that adding languages to SQL 2000 is not supported and
>should not be done.
>I could add the language directly to syslanguages (it works, I've tried
it).
>My question is: Is there actually a risk in adding a new language to
>syslanguages? Are there any factors that I should be aware of?
>Thanks,
>BB
>
>
Thursday, March 8, 2012
Adding New Languages
Labels:
adding,
application,
database,
languages,
microsoft,
multiplelanguages,
mysql,
oracle,
raiserrors,
return,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment