1) executeNativeSql :
-Execute the provided "sqlText" directly within the data source at "dataSourcePath", instead of the Composite server(TDV server) if permitted by the data source. This is only available for data sources that support direct SQL submission.
-Mainly used with general SQL queries.

Example: To create a table using executeNativeSql operation.

1)Configure the published database to accept DDL statements. For more information, please check the User's Guide under "Configuring DDL for a Data Service".

2)Run executeNativeSql
Input:
<execute:executeNativeSql xmlns:execute="http://www.compositesw.com/services/system/admin/execute" xmlns:user="http://www.compositesw.com/services/system/admin/user">
  <execute:sqlText>CREATE Table TestTable (name VARCHAR(20));</execute:sqlText>
  <execute:isBlocking>1</execute:isBlocking>
  <execute:dataSourcePath>/services/databases/publishedDB</execute:dataSourcePath>
</execute:executeNativeSql>

3)Introspect the data source
The table "TestTable" should appear in the introspection dialog.
-------------------------------------------------------------
2) executeSql :
-Execute the provided "sqlText" directly within the Composite server.
-If data service name is provided it will only consider the published resources under "/services/databases/". 
-If data service name is not provided, we need to give the absolute resource references in the "sqlText".
-Mainly used with general SQL queries.
--------------------------------------------------------------
3) executeSqlScript :
-Execute the provided "sqlText" directly within the Composite server.
-Mainly used with SQL scripts/procedures.
-Has a "input" field which is not present in the above mentioned operations.
  Inputs (optional): A list of parameter definitions and values ​​to use as execution inputs.
    <execute:parameter>
      <execute:definition>INTEGER</execute:definition>
      <execute:value>2</execute:value>
    </execute:parameter>

-Does not have a response element "rows", which is present in the above mentioned operations, outputs a result ID instead which can be later used with operations like getTabularResult.

-To know more about executeNativeSql, please refer: https://docs.tibco.com/pub/tdv/8.5.4/doc/html/en-US/StudioHelp/index.html#page/StudioHelp%2FCh_3_OperationsList_45.StudioHelp.html%23

-To know more about executeSql , please refer: https://docs.tibco.com/pub/tdv/8.5.4/doc/html/en-US/StudioHelp/index.html#page/StudioHelp%2FCh_3_OperationsList_47.StudioHelp.html%23

-To know more about executeSqlScript, please refer: https://docs.tibco.com/pub/tdv/8.5.4/doc/html/en-US/StudioHelp/index.html#page/StudioHelp%2FCh_3_OperationsList_49.StudioHelp.html%23