Skip to main content

SQL Server: Storing language specific data in SQL Server table field.

While working on multi language support we need to insert different language data in same field or different fields of a SQL server table.

There are two basic rules one need to keep in mind while storing multi lingual or Unicode data:
·         First is column must be of Unicode data type (i.e., nchar, nvarchar, ntext).
·         And second is that the value must be prefixed with N while insertion.

Below is the sample script with output to understand it better.
-- Drop and Create TestMultiLingualDB
IF db_id('TestMultiLingualDB') IS NOT NULL
      DROP DATABASE TestMultiLingualDB
USE TestMultiLingualDB
CREATE TABLE MultiLanguage (Id INT, Var_Field VARCHAR(50), NVar_Field NVARCHAR(50))
-- Insert Hindi Characters
INSERT INTO MultiLanguage VALUES (1, N'यह एक शब्द है', N'यह एक शब्द है')
-- Insert Punjabi Characters
INSERT INTO MultiLanguage VALUES (2, N'ਇਹ ਇੱਕ ਸ਼ਬਦ ਦਾ ਹੁੰਦਾ ਹੈ', N'ਇਹ ਇੱਕ ਸ਼ਬਦ ਦਾ ਹੁੰਦਾ ਹੈ')
--Select and see inserted values.
SELECT * FROM MultiLanguage
-- Drop TestMultiLingualDB


In the output you can see that value in Var_Field are saved as ????, even though in script N is prefixed while inserting. This is because field is of VARCHAR type.
Id          Var_Field                           NVar_Field
----------- ----------------------------------- -----------------------------------
1           ?? ?? ???? ??                       यह एक शब्द है
2           ?? ??? ???? ?? ????? ??             ਇਹ ਇੱਕ ਸ਼ਬਦ ਦਾ ਹੁੰਦਾ ਹੈ

Note: If you are using a stored procedure to insert the Unicode data, then make sure that N is used before the string while passing the parameter to stored procedure. Also make sure the parameter declared in stored procedure is of Unicode type.

Popular posts from this blog

C#: Merging Excel cells with NPOI HSSFWorkbook

In this post we’ll see how to merge the two or more cell with each other while creating the excel sheet using NPOI.
Mentioned below is code to merge multiple cells, in this example we are merging first cell to fifth cell of first row (you can adjust row or cell range by passing particular parameters in CellRangeAddress).
//Created new Workbook var hwb = new NPOI.HSSF.UserModel.HSSFWorkbook(); //Create worksheet with name. var sheet = hwb.CreateSheet("new sheet"); //Create row and cell. var row = sheet.CreateRow(0); var cell = row.CreateCell(0); ; //Set text inside cell cell.SetCellValue("This is Merged cell"); cell.CellStyle.WrapText = true; //define cell range address // parameters: -> first row to last and first cell to last cell var cra = new NPOI.SS.Util.CellRangeAddress(0, 0, 0, 4); //Add merged region to sheet. sheet.AddMergedRegion(cra);
Hope this solution helps you J

Calculate Sum and average of two or more Textbox values using JQuery

We can calculate sum and average of values entered in textboxes with the help of small piece of jQuery code.
First of all let’s create a HTML form where we’ll ask user to enter marks in each subject, under body section add following HTML:
<tableclass="demo-table"> <trclass="label"> <tdcolspan="2">Please enter marks(0-99):</td> </tr> <tr> <td>English</td> <td> <inputtype="text"class="txtMarks"name="txtMarks"

Difference between Web API, WCF and Web Service

So now we have got the basic idea about Web API, now let’s do some comparison of Web API with WCF and web services.
Web Service WCF Web API Web services created as file with .asmx extension. WCF create with .svc extension Web API are simple class file with .cs(for C#) extension. Web API is inherited from “ApiController” and class name must end with “Controller”. It is SOAP based service and return data in XML form. It is also based on SOAP and return data in XML form. Web API is HTTP based service and by default it return data in JSON or XML form. It supports only HTTP protocol. It supports various protocols like TCP, HTTP, HTTPS, Named Pipes, and MSMQ. It supports HTTP protocol. It can be hosted only on IIS. It can be hosted with in the application or on IIS or using window service. It can be hosted with in the application or on IIS. It is not open source but can be consumed by any client that understands xml. It is not open source but can be consumed by any client t…