Dynamic SQL on Unicode data types

Hello,
We're in the process of converting our database to support Unicode. So, converted the tables to NCHAR/NCHAR2 from CHAR/VARCHAR2. Now, dealing with stored procedures. Here's a stored procedure that's causing issue:(I am just giving the part of the code that's causing issue)
create procedure xx_xxxxx(
v_sql_txt nvarchar2(2000),
P_CV1 IN OUT COM_DEFS.CV_TYP) -- CV_TYP is a ref cursor type declared in COM_DEFS package
as
begin
OPEN p_cv1 FOR v_sql_txt1;
end;
v_sql_txt is built my the application and getting passed to the stored procedure.
It gives an error PLS-00382: expression is of wrong type.
After some digging, I found that NVARCHAR2/NCHAR types are not supported in OPEN .. FOR.
Could someone of you suggest an alternative to this?
Thanks
M.

Apparently you don't understand the difference between characterset and national character and you are heading in a completely incorrect direction.
You should change the characterset of the database NOT the national characterset.
Consequently
- you should NOT change all CHAR to NCHAR and VARCHAR2 to NVARCHAR2
- you should change the NLS_LENGTH_SEMANTICS of the database to CHARACTER (as opposed to BYTE)
Sybrand Bakker
Senior Oracle DBA

Similar Messages

Dynamic sql reurns no data when multiple values are passed.

(Dynamic sql returns no data when multiple values are passed.)
Hi,
While executing the below dynamic sql in the procedure no data is returned when it has multiple input values.
When the input is EMPID := '1'; the procedure works fine and returns data.Any suggestion why the procedure doen't works when input as EMPID := '1'',''2'; is passed as parameter?
=======================================================
create or replace PROCEDURE TEST(EMPID IN VARCHAR2, rc OUT sys_refcursor)
IS
stmt VARCHAR2(9272);
V_EMPID VARCHAR2(100);
BEGIN
V_EMPID :=EMPID;
stmt := 'select * from TEST123 where Empid is NOT NULL';
IF V_EMPID <> '-1' THEN
stmt := stmt || ' and Empid in (:1)';
ELSE
stmt := stmt || ' and -1 = :1';
END IF;
OPEN rc FOR stmt USING V_EMPID;
END Z_TEST;
============================================================
Script for create table
==================================================================
CREATE TABLE TEST123 (
EMPID VARCHAR2(10 BYTE),
DEPT NUMBER(3,0)
===========================================
Insert into PDEVUSER.TEST123 (EMPID,DEPT) values ('1',20);
Insert into PDEVUSER.TEST123 (EMPID,DEPT) values ('2',10);
Insert into PDEVUSER.TEST123 (EMPID,DEPT) values ('3',30);
Insert into PDEVUSER.TEST123 (EMPID,DEPT) values ('3',30);
Insert into PDEVUSER.TEST123 (EMPID,DEPT) values ('2',10);
=============================================
Select * from TEST123 where Empid in (1,2,3)
EMPID DEPT
1     20
2     10
3     30
3     30
2     10
===================================================================
Any suggestion why the procedure doen't works when input EMPID := '1'',''2';?
Thank you,

The whole scenario is a little strange. When I tried to compile your procedure it couldn't compile, but I added the missing info and was able to get it compiled.
create or replace PROCEDURE TEST (EMPID IN VARCHAR2, rc OUT sys_refcursor)
IS
stmt        VARCHAR2 (9272);
V_EMPID     VARCHAR2 (100);
BEGIN
V_EMPID := EMPID;
stmt := 'select * from TEST123 where Empid is NOT NULL';
IF V_EMPID = '-1' THEN
    stmt := stmt || ' and Empid in (:1)';
ELSE
    stmt := stmt || ' and -1 = :1';
END IF;
OPEN rc FOR stmt USING V_EMPID;
END;If you pass in 1 as a parameter, it is going to execute because the statement that it is building is:
select * from TEST123 where Empid is NOT NULL and -1 = 1Although the syntax is valid -1 will never equal 1 so you will never get any data.
If you pass in 1,2 as a parameter then it is basically building the following:
select * from TEST123 where Empid is NOT NULL and -1 = 1,2This will cause an invalid number because it is trying to check where -1 = 1,2
You could always change your code to:
PROCEDURE TEST (EMPID IN VARCHAR2, rc OUT sys_refcursor)
IS
stmt        VARCHAR2 (9272);
V_EMPID     VARCHAR2 (100);
BEGIN
V_EMPID := EMPID;
stmt := 'select * from TEST123 where Empid is NOT NULL';
stmt := stmt || ' and Empid in (:1)';
OPEN rc FOR stmt USING V_EMPID;
END;and forget the if v_empid = '-1' check. If you pass in a 1 it will work, if you pass in 1,2 is will work, but don't pass them in with any tick marks.

Dynamic sql to insert data in table

hi
I wish to insert 5 records in a table at runtime.
i.e the data should be entered at runtime.
I tried using a for loop but failed ..
I think it is possible thru dynamic sql ...
could someone help me out ..
regards
susmitha

If your database is 8 or above, you might want to try something like:
for i in 1..5 loop
execute immediate 'insert into table_name ' ||
'(your_field) values (your_value)';
end loop;
If your databasae is lower than 8, then you will have to use dbms_sql command instead. Hope this helps.

Dynamic structure of "string" data type. Please help.

ABAPers,
I am calling cl_alv_table_create=>create_dynamic_table method to dynamically create a structure. The input structure definition is as follows:
data: xfc type lvc_s_fcat.
data: ifc type lvc_t_fcat.
* define Fld1
clear xfc.
xfc-fieldname = 'Fld1'.
xfc-datatype = 'string'.
append xfc to ifc.
* define Fld2
clear xfc.
xfc-fieldname = 'Fld2'.
xfc-datatype = 'string'.
append xfc to ifc.
Although the call to create_dynamic_table does not throw any exceptions, it appears Fld1 and Fld2 are not of "string" data type. I don't know of a way to see what type they are. However, they do have a length limit of 10 characters.
After some experimenting, it turns out that the method simply ignores "datatype" value if it doesn't understand it and creates the field with some default data type.
I would appreciate it if someone can show me how to create fields of "string" data type.
Thank you in advance for your help.
Pradeep

That's right, use STRG as the datatype. Please see the example program.
report zrich_0003.
type-pools: slis.
data: new_table type ref to data,
      new_line type ref to data.
data: xfc type lvc_s_fcat,
       ifc type lvc_t_fcat.
field-symbols: <dyn_table> type standard table,
               <dyn_wa>,
               <fs>.
start-of-selection.
clear xfc.
xfc-fieldname = 'Field1' .
xfc-datatype = 'STRG'.
append xfc to ifc .
clear xfc.
xfc-fieldname = 'Field2' .
xfc-datatype = 'STRG'.
append xfc to ifc .
* Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
    exporting
      it_fieldcatalog = ifc
    importing
      ep_table        = new_table.
assign new_table->* to <dyn_table>.
* Create dynamic work area and assign to FS
create data new_line like line of <dyn_table>.
assign new_line->* to <dyn_wa>.
assign component 1 of structure <dyn_wa> to <fs>.
<fs> = 'This is string 1'.
assign component 2 of structure <dyn_wa> to <fs>.
<fs> = 'This is string 2'.
append <dyn_wa> to <dyn_table>.
* Write the values of internal table.
loop at <dyn_table> into <dyn_wa>.
    do.
      assign component sy-index of structure <dyn_wa> to <fs>.
      if sy-subrc <> 0.
        exit.
      endif.
      write:/ <fs>.
    enddo.
endloop.
REgards,
Rich Heilman

How to dynamic set messageInputText item data type?

Hi,
I have a LOV and other messageInputText items on the page. I need to be able to change the messageInputText item data type based on the value selected from LOV. How can I do that?
DD

1)Allow PPR on the item that receives the LOV values
2)Edit the VO query and create a SQL based column, which in turn will control the switcher. Something like –
decode(nvl(to_char(EmployeeEO.END_DATE), 'N'), 'N', 'DataType1', 'DataType2') AS DELETE_SWITCHER
3)Now add a switcher region with two cases in your page. Each case should represent the two possible values defined in the SQL based column ( “DataType1”, DataType2” in the above example).
4)Add two messageTextInput items under each case, but with different datatypes.

Sql server 2000 data type

In sql server 2000, what data type do I use for a field that
needs to show two decimal places? It is a weight field, so the
weight in ounces could be something like 12.25 and it needs to
store it this way in the database. I'm kind of new to sql server,
so any help would be greatly appreciated!

You asked "In sql server 2000, what data type do I use for a
field that needs to show two decimal places?" and I answered
"decimal and numeric". How much clearer could I be?
Numeric data types with fixed precision and scale.
decimal[(p[, s])] and numeric[(p[, s])]
Fixed precision and scale numbers. When maximum precision is
used, valid values are from - 10^38 +1 through 10^38 - 1. The
SQL-92 synonyms for decimal are dec and dec(p, s).
p (precision)
Specifies the maximum total number of decimal digits that can
be stored, both to the left and to the right of the decimal point.
The precision must be a value from 1 through the maximum precision.
The maximum precision is 38.
s (scale)
Specifies the maximum number of decimal digits that can be
stored to the right of the decimal point. Scale must be a value
from 0 through p. The default scale is 0; therefore, 0 <= s
<= p. Maximum storage sizes vary, based on the precision.
I recommend that you load SQL Server Books Online on your
computer, as it is available free from Microsoft as a download and
it has everything you will probably need to know about SQL Server.
Or you could just use the online version at
SQL
Server 2000 Books Online
Phil

Importing an SQL Server TEXT data type field in Oracle - problem with LONG

Hello,
I work in Oracle 9i and I created a view on a distant SQL Server database that contains a TEXT data type field. But I have a problem when I select that field in Oracle; I have the following error message: "ORA-00997: forbidden use of LONG data type".
Could anybody have a solution for me, to solve that problem?
Thanks a lot!

It is very difficult to suggest anything without seeing your code. I don't even know if what you are seeing is the actual value or an error code. Often, negative numbers are indicative of error codes.
For instance -1 could mean that you have an invalid reference or path, etc...
Can you post your code?

MS SQL Server 2005 data types

Hi,
I have some code that executes a stored procedure in SQL Server 2005 database from Weblogic 8.1. There is a Spring framework layer in between. I am having problems passing a datetime parameter to the SP (ther server thinks it's a varchar). According to the BEA documentation here http://edocs.bea.com/wls/docs100/jdbc_drivers/mssqlserver.html#wp1088746, a datetime parameter should be passed as java.sql.Types.TIMESTAMP. I've tried TIMESTAMP, DATE, TIME, and none of them work. But, that documentation says it's only for SQL Server 2000. What about 2005? Does anyone know?
Thanks in advance.

We use SQL2005 & WebLogic 8.1, but we use the Microsoft JDBC driver form here
and it all works fine with timestamps. We use this datatype to pass them down java.sql.Timestamp
http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en
The MS driver has some enhancements specifically for SQL2005 for performance and handling the new data types. We've always been told to use the vendors driver in preference to the BEA supplied one - that came from BEA!
Pete

Convert MS SQL server image data type into oracle clob

Hi all! I'm tryng to access to Microsoft SQL server with Oracle via ODBC. Oracle is not able to use the image data type of Microsoft SQL server. Do you know a way to convert this data type in an oracle format? The explicit casting converts image to long raw, but after the conversion Oracle is not able to manage these data type. Thank you very much!
Stefano.

Hi you might want to post your question in General Forum.
General Database Discussions
There's very few users visit this forum.

How to migrate SQL Server image data type to Oracle 8 BLOB data type?

Hi,
I have to migrate data from sql server to Oracle 10 g.
I am unable to migrate image data type from sql server to blob data type in oracle.
Iam using Oracle Heterogenous Services to migrate the data,Using Merge statement and database link.
I am getting the following error-
ERROR at line 7:
ORA-00932: inconsistent datatypes: expected BLOB got LONG BINARY
Can any one suggest me how to migrate Image datatype to BLOB???

Hi you might want to post your question in General Forum.
General Database Discussions
There's very few users visit this forum.

SQL Insert Statement Data Type Mismatch Error

I am doing a very simple web application that has a Microsoft Access database as the data source. I have been able to sucessfully create update and query statements using parameters but am having issues with an insert statement. I am using JSTL 1.1.2
The following code creates the data type mismatch error.
<sql:update
     sql="insert into tblTtoF(TFToolID,TFFeatID) values(?,?)">
        <sql:param value='$(ID}'/>
     <sql:param value='${feature}'/>
        </sql:update>The table has NUMBER as the data type for both of these fields and the variables I am feeding into it are both numbers. If I hard code the first number into the sql statement then it works. I have tried swapping the variables around and as long as the first one is hard coded the parameter for the second one works no matter which is first or second.
However I can get the following code to work, which of course leaves me vulnerable to sql injection attacks which is not really a good thing.
<sql:update>
     insert into tblTtoF(TFToolID,TFFeatID) values('<c:out value="${ID}"/>','<c:out value="${feature}"/>')
        </sql:update>So I am just looking for any suggestions as to why my first piece of code doesn't work seeing as it is the simplest of SQL statements and the most standard syntax.
Thanks

I changed it to the following
     <c:set var="featurenew" value="${0 + feature}"/>
     <c:set var="IDnew" value="${0 + param.toolID}"/>
          <sql:update
          sql="insert into tblTtoF(TFToolID,TFFeatID) values(?,?)">
          <sql:param value='$(IDnew}'/>
          <sql:param value='${featurenew}'/>
          </sql:update>And got the following error in the localhost.log
31/07/2006 09:31:41 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.sql.SQLException: SQL Exception : [Microsoft][ODBC Microsoft Access Driver]Optional feature not implemented
     at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setObject(JdbcOdbcPreparedStatement.java:1437)
     at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setObject(JdbcOdbcPreparedStatement.java:1072)
     at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setObject(JdbcOdbcPreparedStatement.java:1063)
     at org.apache.taglibs.standard.tag.common.sql.UpdateTagSupport.setParameters(UpdateTagSupport.java:254)
     at org.apache.taglibs.standard.tag.common.sql.UpdateTagSupport.doEndTag(UpdateTagSupport.java:156)
     at org.apache.jsp.dataUpdated_jsp._jspx_meth_sql_update_1(dataUpdated_jsp.java:975)
     at org.apache.jsp.dataUpdated_jsp._jspx_meth_c_if_0(dataUpdated_jsp.java:879)
     at org.apache.jsp.dataUpdated_jsp._jspx_meth_c_forEach_0(dataUpdated_jsp.java:680)
     at org.apache.jsp.dataUpdated_jsp._jspService(dataUpdated_jsp.java:151)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:833)
     at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:639)
     at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1285)
     at java.lang.Thread.run(Thread.java:595)
I have also tried the following in the past with no luck
<fmt:parseNumber value="${ID}" type="number" var="IDnew"/>
AND......
<sql:query
   sql="select TFToolID from tblTtoF where TFToolID = ?"
   var="toolresults">
   <sql:param value="${ID}"/>
</sql:query>
<c:forEach var="getID" items="${toolresults.rows}">
     <c:set var="theID" value="${getID.TFToolID}"/>
</c:forEach>
AND when that didn't work, added this....
<fmt:parseNumber value="${theID}" var="IDnew"/>

Will SQL Developer support data type anydata

Will SQL Developer support datatype sys.anydata in future releases?
Currently SQL Developer will not show any data for columns of type anydata.
Example:
create table t1 (id number, col1 sys.anydata);
insert into t1 values(1,sys.anydata.convertvarchar2('TEST'));
IF I export data from this table something like
Insert into T1 (ID,COL1) values (1,'SYS.ANYDATA'); will be generated.
The grid will display 'sys.anydata' for this column
Versions:
WINXP SP3
SQL Developer Version 2.1.1.64
Build MAIN-64.39
Ernst

I added a feature request:
https://htmldb.oracle.com/pls/otn/f?p=42626:39:528125578772603::NO::P39_ID:25161
Regards,
Ernst
Edited by: Ernst Leber on May 31, 2010 12:36 PM

MS Sql + java.util.Date type

Hi,
In MySql everything is ok, but in MS Sql I get this error and bouth with timedate type in the database:
22/11/2006 16:34:59 org.jdesktop.dataset.provider.sql.SQLCommand getUpdateStatement
WARNING: Problem with update SQL statement null
22/11/2006 16:34:59 org.jdesktop.dataset.provider.sql.SQLCommand getUpdateStatement
WARNING: The Java type java.util.Date is not a supported type.
com.microsoft.sqlserver.jdbc.SQLServerException: The Java type java.util.Date is not a supported type.
===========
My code:
===========
Date newDate = dateReminder.getDate();
miliSecDate = newDate2.getTime();
s = spinner.getTime();
timeStr = s.split(":");
miliSecTimeS = Long.parseLong(timeStr[1].trim());
miliSecTime = ((miliSecTimeH * 60 * 60) + (miliSecTimeS * 60)) * 1000;
newDate2.setTime(miliSecTime + miliSecDate);

Even if I set myJDatepicker.getDate()
I get the same error.
my code:
GlobalTablesProperties.getInstance().getProvider()
.getCommand().setParameter("date", myJDatepicker.getDate());
GlobalTablesProperties.getInstance().getProvider()
.save(
GlobalTablesProperties.getInstance().getTaskData());
JDBCDataConnection jdbcConn = (JDBCDataConnection) (GlobalTablesProperties.getInstance().getProvider().getConnection());
jdbcConn.commit();
GlobalTablesProperties.getInstance().getSelectedDataModel()
.setValue("date", myJDatepicker.getDate());

Unicode and non-unicode string data types Issue with 2008 SSIS Package

Hi All,
I am converting a 2005 SSIS Package to 2008. I have a task which has SQL Server as the source and Oracle as the destination. I copy the data from a SQL server view with a field nvarchar(10) to a field of a oracle table varchar(10). The package executes fine
on my local when i use the data transformation task to convert to DT_STR. But when I deploy the dtsx file on the server and try to run from an SQL Job Agent it gives me the unicode and non-unicode string data types error for the field. I have checked the registry
settings and its the same in my local and the server. Tried both the data conversion task and Derived Column task but with no luck. Pls suggest me what changes are required in my package to run it from the SQL Agent Job.
Thanks.

What is Unicode and non Unicode data formats
Unicode :
A Unicode character takes more bytes to store the data in the database. As we all know, many global industries wants to increase their business worldwide and grow at the same time, they would want to widen their business by providing
services to the customers worldwide by supporting different languages like Chinese, Japanese, Korean and Arabic. Many websites these days are supporting international languages to do their business and to attract more and more customers and that makes life
easier for both the parties.
To store the customer data into the database the database must support a mechanism to store the international characters, storing these characters is not easy, and many database vendors have to revised their strategies and come
up with new mechanisms to support or to store these international characters in the database. Some of the big vendors like Oracle, Microsoft, IBM and other database vendors started providing the international character support so that the data can be stored
and retrieved accordingly to avoid any hiccups while doing business with the international customers.
The difference in storing character data between Unicode and non-Unicode depends on whether non-Unicode data is stored by using double-byte character sets. All non-East Asian languages and the Thai language store non-Unicode characters
in single bytes. Therefore, storing these languages as Unicode uses two times the space that is used specifying a non-Unicode code page. On the other hand, the non-Unicode code pages of many other Asian languages specify character storage in double-byte character
sets (DBCS). Therefore, for these languages, there is almost no difference in storage between non-Unicode and Unicode.
Encoding Formats:
Some of the common encoding formats for Unicode are UCS-2, UTF-8, UTF-16, UTF-32 have been made available by database vendors to their customers. For SQL Server 7.0 and higher versions Microsoft uses the encoding format UCS-2 to store the UTF-8 data. Under
this mechanism, all Unicode characters are stored by using 2 bytes.
Unicode data can be encoded in many different ways. UCS-2 and UTF-8 are two common ways to store bit patterns that represent Unicode characters. Microsoft Windows NT, SQL Server, Java, COM, and the SQL Server ODBC driver and OLEDB
provider all internally represent Unicode data as UCS-2.
The options for using SQL Server 7.0 or SQL Server 2000 as a backend server for an application that sends and receives Unicode data that is encoded as UTF-8 include:
For example, if your business is using a website supporting ASP pages, then this is what happens:
If your application uses Active Server Pages (ASP) and you are using Internet Information Server (IIS) 5.0 and Microsoft Windows 2000, you can add "<% Session.Codepage=65001 %>" to your server-side ASP script.
This instructs IIS to convert all dynamically generated strings (example: Response.Write) from UCS-2 to UTF-8 automatically before sending them to the client.
If you do not want to enable sessions, you can alternatively use the server-side directive "<%@ CodePage=65001 %>".
Any UTF-8 data sent from the client to the server via GET or POST is also converted to UCS-2 automatically. The Session.Codepage property is the recommended method to handle UTF-8 data within a web application. This Codepage
setting is not available on IIS 4.0 and Windows NT 4.0.
Sorting and other operations :
The effect of Unicode data on performance is complicated by a variety of factors that include the following:
1. The difference between Unicode sorting rules and non-Unicode sorting rules
2. The difference between sorting double-byte and single-byte characters
3. Code page conversion between client and server
Performing operations like >, <, ORDER BY are resource intensive and will be difficult to get correct results if the codepage conversion between client and server is not available.
Sorting lots of Unicode data can be slower than non-Unicode data, because the data is stored in double bytes. On the other hand, sorting Asian characters in Unicode is faster than sorting Asian DBCS data in a specific code page,
because DBCS data is actually a mixture of single-byte and double-byte widths, while Unicode characters are fixed-width.
Non-Unicode :
Non Unicode is exactly opposite to Unicode. Using non Unicode it is easy to store languages like ‘English’ but not other Asian languages that need more bits to store correctly otherwise truncation will occur.
Now, let’s see some of the advantages of not storing the data in Unicode format:
1. It takes less space to store the data in the database hence we will save lot of hard disk space.
2. Moving of database files from one server to other takes less time.
3. Backup and restore of the database makes huge impact and it is good for DBA’s that it takes less time
Non-Unicode vs. Unicode Data Types: Comparison Chart
The primary difference between unicode and non-Unicode data types is the ability of Unicode to easily handle the storage of foreign language characters which also requires more storage space.
Non-Unicode
Unicode
(char, varchar, text)
(nchar, nvarchar, ntext)
Stores data in fixed or variable length
Same as non-Unicode
char: data is padded with blanks to fill the field size. For example, if a char(10) field contains 5 characters the system will pad it with 5 blanks
nchar: same as char
varchar: stores actual value and does not pad with blanks
nvarchar: same as varchar
requires 1 byte of storage
requires 2 bytes of storage
char and varchar: can store up to 8000 characters
nchar and nvarchar: can store up to 4000 characters
Best suited for US English: "One problem with data types that use 1 byte to encode each character is that the data type can only represent 256 different characters. This forces multiple
encoding specifications (or code pages) for different alphabets such as European alphabets, which are relatively small. It is also impossible to handle systems such as the Japanese Kanji or Korean Hangul alphabets that have thousands of characters."<sup>1</sup>
Best suited for systems that need to support at least one foreign language: "The Unicode specification defines a single encoding scheme for most characters widely used in businesses around the world.
All computers consistently translate the bit patterns in Unicode data into characters using the single Unicode specification. This ensures that the same bit pattern is always converted to the same character on all computers. Data can be freely transferred
from one database or computer to another without concern that the receiving system will translate the bit patterns into characters incorrectly.
https://irfansworld.wordpress.com/2011/01/25/what-is-unicode-and-non-unicode-data-formats/
Thanks Shiven:) If Answer is Helpful, Please Vote

Error when insert data in Sql Server table(DateTime data type)

Hello all,
I have created a database link in oracle 11g to SQL Server 2008 using Sqlserver gateway for oracle,Oracle run on Linux and SQL Server run on Windows platform.
I have queried a table and it fetches rows from the target table.
I am using this syntax for insert a row in Sql Server table.
Insert into Prod@sqlserver (NUMITEMCODE, NUMPREOPENSTOCK, NUMQNTY, NUMNEWOPENSTOCK, DATPRODDATE , TXTCOMPANYCODE, "bolstatus", NUMRESQNTY )
Values (1118 , 1390.0 , 100.0 ,1490 , '2012-06-23 12:37:58.000','SFP' ,0 , 0 );
but it give me error on DATPRODDATE,The data type of DATPRODDATE column in Sql Server is DATETIME.
My Question is how can i pass the date values in INSERT statement for Sql Server DateTime data type.
Regards

Just as with Oracle, you have to specify the date using the to_date() function or use the native date format for the target database (if you can figure out what that is). This is good practice anyway and a good habit to get into.

Dynamic SQL on Unicode data types

Similar Messages

Maybe you are looking for