Related to messages

[Former Member]

Hi Experts,

Hope you are doing well, Could anyone please reply to this question.

Difference between native sql and XML sql ?

[justin_santhanam]

Hi,

Keep this link as reference -http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

The difference between XML -SQL and native SQL is the strucuture which you design.

If you design the strucutre like

XML-SQL

<StatementName1>

<EmpTable action="UPDATE">

<access>

<Country>US</Country>

<Status>Active</Status>

</access>

<key1>

<EmpID>126376</EmpID>

</key1>

</EmpTable>

</StatementName1>

In the above example - The SQL structure is in the XML elements, hence the adapter will convert the above strcuture into the following query like

Update EmpTable set Country ='US' , Status ='Active' where EmpID ='126376'

Native-SQL

<root>

<stmt>

<EmpTable action="SQL_DML">

<access> UPDATE EmpTable SET Country=’US’, Status=’Active' WHERE EmpID='$EmpID$’

</access>

<key>

<EmpID>126376</EmpID>

</key>

</EmpTable>

</stmt>

</root>

In the above the structure the structure expects the actual SQL-Query.

This is the difference!

raj.

[agasthuri_doss]

Hi,

Native SQL:

1) Native SQL is real SQL for database in use. It means beside OPEN SQL, if we need wecan use the native SQL for databases. Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary, and therefore integrate data that is not part of the R/3 System.

Native SQL Advantages :

1) Tables are not declared in ABAP Dictionary can be accessed. (e.g. Tables belonging to sys or system

user of Oracle, etc.)

2 ) To use some of the special features supported by the database-specific SQL. (e.g. Passing hints to

Oracle optimizer.)

Native SQL Disadvanteges:

1) No syntax check is performed whatever is written between EXEC and ENDEXEC.

ABAP program containing database-specific SQL statements will not run under different database systems.

2)There is no automatic clien handling for client dependent tables.

Care has to be taken during migration to higher versions.

SQL/XML :

SQL/XML refers to the XML extensions of SQL. These are developed by INCITS H2.3, with participation from Oracle, IBM, Microsoft (which does not plan to implement SQL/XML), Sybase, and DataDirect Technologies. In SQL 2003, these extensions include:

1) XML Publishing Functions

2) The XML Datatype

3) Mapping Rules

SQL/XML Mapping Rules:

The XML publishing functions use SQL values to create XML values, and these XML values have W3C XML Schema types. When we discussed the XML publishing functions, we did not address specifically how the XML representation is determined. The mapping rules of SQL/XML describe in excruciating detail how SQL values can be mapped to and from XML values, and how SQL metadata can be mapped to and from W3C XML Schemas. To give a flavor for the level of detail in which this is specified, here are the equivalent headings from the SQL/XML specification's table of contents:

a) Mapping SQL character sets to Unicode.

b) Mapping SQL <identifier>s to XML Names.

c) Mapping SQL data types (as used in SQL-schemas to define SQL-schema objects such as columns) to

XML Schema data types.

d) Mapping values of SQL data types to values of XML Schema data types.

e) Mapping an SQL table to an XML document and an XML Schema document.

f) Mapping an SQL schema to an XML document and an XML Schema document.

g) Mapping an SQL catalog to an XML document and an XML Schema document.

h) Mapping Unicode to SQL character sets.

i) Mapping XML Names to SQL <identifier>s.

Regards

Sangeetha

Edited by: Sangeetha on Mar 30, 2008 5:45 PM

Edited by: Sangeetha on Mar 30, 2008 5:46 PM