We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

DATA LENGTH IN JAPANESE SQL SERVER

vram
vram asked
on
Medium Priority
616 Views
Last Modified: 2011-09-20
My Problem : I  am using SQL server 6.5 as backend for storing data. I have a table with a field of length 20.

In case of English SQL Server I can store 20 english characters. But in case of Japanese SQL server for the
same table I can only store maximum of 10 Japanese characters.

My question is
1) how  to handle the problem in both the SQL
servers without changing the data length so that I can store 20 characters.My requirement is to use same table
creation scripts for both the servers.
Comment
Watch Question

Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
I am pretty satisfied about ur answer, but i find that when i use nvarchar(n) in a create table statement for eg:
create table x
(fld1 nvarchar(2) )  it gives an error saying nvarchar not found.
How do i use nvarchar(n) or nchar(n)  ?
kindly clarify immediately
MOHAN

Author

Commented:
I am pretty satisfied about ur answer, but i find that when i use nvarchar(n) in a create table statement for eg:
create table x
(fld1 nvarchar(2) )  it gives an error saying nvarchar not found.
How do i use nvarchar(n) or nchar(n)  ?
kindly clarify immediately
SQL SERVER VER 6.5 [JAPANESE VERSION]
If any new versions available with the above feature (nvarchar(n)) kindly mention
MOHAN

Commented:
This is exactly what I did..dunno why it doesn't work for you..
1> create table jit1
2> (field2 nvarchar(2))
3> go
1> sp_help jit1
2> go
 Name                           Owner
         Type
 ------------------------------ ------------------------------
        ----------------------
 jit1                           dbo
         user table

 Data_located_on_segment        When_created
 ------------------------------ --------------------------
 default                               Aug  4 1998  9:21AM

 Column_name     Type            Length Prec Scale Nulls Default_name
         Rule_name       Identity
 --------------- --------------- ------ ---- ----- ----- ---------------
        --------------- --------
 field2          nvarchar             2 NULL  NULL     0 NULL
         NULL                   0
Object does not have any indexes.
No defined keys for this object.
Object is not partitioned.

Commented:
Also just so that you know..MS SQL server did not have this in version 6.5..they introduced it in version 7.0. They call it Unicode. So just in ase you are running on 6.5 obviously it doesn't work. They introduced nchar in 6.5 but the full functionality of multibyte character sets have only been introduced in version 7.

The fact that Unicode data needs twice much storage space is ofset by the elimination of the need to convert extended characters between code pages. In MS SQL Server , the new data types that support Unicode are ntext, nchar andd nvarchar. They are the same as text, char and varchar, except for the wider range of characters supported and the increased storage space used.

Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.