Use of salrt table in XI

Hi Experts,
What is the use of SALRT, SXMSCLUP and SXMSCLUR table in XI.
Please explain what it is doing exactly and in which cases they are using,
your explanation is really helpful for me.
Regards,
Madhu.

Hi Madhu,
These tables are used to store the payload XML data, in BLOB format. Refer to this the below link to find the uses of various tables in PI
XI Tables - Process Integration - SCN Wiki

Similar Messages

How to use customer extension table for schedule line for shopping cart ?

Dear Experts,
One of our client wants to have schedule lines in shopping cart item. I am thinking of using customer extension table at item level for shopping cart. Could you please help me on how I should proceed with the appending the structures so that the end user can fill the shopping cart schedule line details?
Which fields should I consider in such cases?
Thanks and regards,
Ranjan

Hi.
I guess you use SRM 7.0. Please go to IMG.
SRM -> SRM Server -> Cross-Application Basic Settings -> Extensions and Field Control (Personalization) -> Create Table Extensions and Supply with Data
Regards,
Masa

How do I use the option "table view" in NetWeaver 2004s Query Designer?

Dear,
We have used NetWeaver 2004s Query Designer, We found a strange problem. The option to select table view is not available. It is greyed out. How can you select table view (tabular) in 2004s Query Designer?
I have read the help doc about tabular view of NetWeaver 2004s Query Designer, I check my query, it has only one structure . but the option is still greyed out. I rebuild the query with 3.x Query Designer in tabular view, and reopen it with 2004s Query Designer, So there is a tab named "tabular view" display, but the option to select table view is still not available, and when users view the query result in web , it is still not in tabular view display. So I am confused, is there a bug with NetWeaver 2004s Query Designer?
Please help me. Thanks!

Note 1002271. Seach this note to use key word "table view"

How to create olap cube using Named Query Table in Data source View

I Create on OLAP Cube using Existing Tables Its Working Fine But When i Use Named Query Table with RelationShip To other Named query Table It Not Working .So give me some deep Clarification On Olap Cube for Better Understanding
Thanks

Hi Pawan,
What do you mean "It Not Working"？ As Kamath said, please post the detail error message, so that we can make further analysis.
In the Data Source View of a CUBE, we can define a named query. In a named query, you can specify an SQL expression to select rows and columns returned from one or more tables in one or more data sources. A named query is like any other table in a data source
view (DSV) with rows and relationships, except that the named query is based on an expression.
Reference:Define Named Queries in a Data Source View (Analysis Services)
Regards,
Charlie Liao
TechNet Community Support

How to use single buffered table with FOR ALL ENTRIES KEYWORD

Hai,
I'm Using TJ02T Database table, It is single buffered table but at the same time I want to use FOR ALL ENTRIES KEYWORD , Please Help me.
Regards,
S.Janani

Hi,
FOR ALL ENTRIES will not depend on the buffering nature of the table. The single buffered table will only only buffer one record into memory. You can still use the statement to query the values, but it may have performance problems if the data volume is high since the records are not completely buffered into memory, the time will spent in getting data from DB.
Thanks..
Preetham S

How to use PL/SQL table

Hi all,
can you guys suggest me how can I use pl/sql tables for the below query to incresing the performance.
DECLARE
    TYPE cur_typ IS REF CURSOR;
    c           cur_typ;
    total_val varchar2(1000);
    sql_stmt varchar2(1000);
    freeform_name NUMBER;
    freeform_id NUMBER;
    imgname_rec EMC_FTW_PREVA.EMC_Image_C_Mungo%rowtype;
    imgval_rec EMC_FTW_PREVA.EMC_Content_C_Mungo%rowtype;
    CURSOR imgname_cur IS
        select * from EMC_FTW_PREVA.EMC_Image_C_Mungo
        where cs_ownerid in (
                    select id from EMC_FTW_PREVA.EMC_Image_C
                    where updateddate > '01-JUN-13'
                    and path is not null
                    and createddate != updateddate)
        and cs_attrid = (select id from EMC_FTW_PREVA.EMC_ATTRIBUTE where name = 'Image_Upload');
BEGIN
    OPEN imgname_cur;
    LOOP
      FETCH imgname_cur INTO imgname_rec;
      EXIT WHEN imgname_cur%NOTFOUND;
      total_val := 'EMC_Image_C_' || imgname_rec.cs_ownerid;
      sql_stmt := 'SELECT instr(textvalue,''' || total_val || '''), cs_ownerid FROM EMC_FTW_PREVA.EMC_Content_C_Mungo a Where cs_attrid = (select id from EMC_FTW_PREVA.EMC_ATTRIBUTE where name = ' || '''' || 'Body_freeform' || '''' || ')';
        OPEN c FOR sql_stmt;
        LOOP
          FETCH c INTO freeform_id,freeform_name;
          EXIT WHEN c%NOTFOUND;
                                  IF freeform_id > 0 THEN
            dbms_output.put_line (imgname_rec.cs_ownerid || ',' || total_val || ',' || freeform_id || ',' || freeform_name);
                                  END IF;
        END LOOP;
        CLOSE c;
   END LOOP;
   CLOSE imgname_cur;
END;
Thanks in Advance.

can you guys suggest me how can I use pl/sql tables for the below query to incresing the performance.
There would be absolutely no point at all in improving the performance of code that has NO benefit.
The only result of executing that code is to possibly produce some lines of output AFTER the entire procedure if finished:
dbms_output.put_line (imgname_rec.cs_ownerid || ',' || total_val || ',' || freeform_id || ',' || freeform_name);
So first you need to explain:
1. what PROBLEM you are trying to solve?
2. why you are trying to use PL/SQL code to solve it.
3. why are you using 'slow by slow' (row by row) processing and then, for each row, opening a new cursor to query more data?
You should be using a single query rather than two nested cursors. But that begs the question of what the code is even supposed to be doing since the only output is going to a memory buffer.

How can i print reports to different printer by use Trigger on table after insert

Hello,
Please can any one tell me how can i print (any message) to different printer (network & local printer) by use Trigger on table after insert.
regards,
Linda.

What you want to do cannot be done with PL/SQL, which does have any print utilities. However you could write something using Java Stored Procedures.
Of course the "different printer" bit will have to be data driven as triggers are not interactive.
rgds, APC

How to load the data using a plsql table in ODI.

Hi All ,
Can anyone help me on this ?
We have a PLSQL procedure which returns a plsql table as out parameter.
We are supposed to load the data in to a file using this plsql table (Table type) in ODI.
Can this be done using ODI?
Regards,
Karthik+

Hi,
We have one process with a ref cursor (Oracle) as a source and remote Oracle DB as a target. I ended up writing my own KM that populates a global temporary table from the cursor first and then transfers the data to target. If temporary table is an option for you, the rest is pretty easy.
Regards.

Error while loading metadata in HPCM application using Import Staging table

Hello All,
I was loading metadata in HPCM using Import Staging table. I successfully uploaded Driver Definition metadata.
However while loading "Driver Exception" metadata, I am not able to load it successfully. I have checked the HPCM logs but found nothing. I then checked the "Import Exception" table and found the following error message.
ERROR_POPULATED_DIM_COLUMNS_DO_NOT_MATCH_STAGE_DEFINITIONCan anyone please help me with this.
Regards,
-SM

It is a bug and there is a patch available.
Oracle Support - "Bug 12905298 : INTERFACE FAILS TO INTEGRATE ON STEP "LOAD DATA INTO PLANNING"
Patch = 12905298: INTERFACE FAILS TO INTEGRATE ON STEP "LOAD DATA INTO PLANNING"
Cheers
John
http://john-goodwin.blogspot.com/

Error occured while provisioning using Database Application Table connector

Hi,
I am trying to provision using Database Application Table connector and OIM 10g. Provisioning is successful but the child data is not sitting in the database. Getting the below error
Response: GCPROV.ProvTransportProvider.DBProvisioningTransport.The column key_id does not exist in the target
Response Description: Unknown response received
Notes:
Assigned to Group : SYSTEM ADMINISTRATORS
Error Details
Setting task status... "GCPROV.ProvTransportProvider.DBProvisioningTransport.The column key_id does not exist in the target" does not correspond to a known Response Code. Using "UNKNOWN".
Please help
Thanks in advance
Sahana

Make sure that your DataSource is in running state when you create the connection pool in DBAdapter. You may restart the server or recreate the connection pool in DBAdapter.
Regards,
Anuj

How to find out that particular structure is used in which tables

Hello Friends,
Most of the times through techinal information we come to know the table name for a particular field.And in se16 when i give that table name than system says its structure and not the table.So in se11 when i give that structure name in database table field, its shows all the field in that structure, but not the data stored in that field.
So my question is how to find out that particular structure is used in which tables,so that i can view data stored in that structure?
Thanking you guys in advance.
Regards,
Jitendra

Dear,
When you click on the technical information it will give the structure name and field, double click on the structure and it will take you the display structure screen, there you will have the where-used List icon (Ctrl + Shift + F3) at the top , click on that and it will show the options, select Database tables and execute, it will give the tables related to the structure, you can explore the list of tables and find where your required field is stored in them.
Thanks & Regards,
Vijaya Bhaskar A

How to populate field catalogue fields in ALV using dynamic internal table

Hi All,
Please let me know how to populate field catalogue fields in ALV using dynamic internal table.
I have created <dyn_table> using code below.
CALL METHOD cl_alv_table_create=>create_dynamic_table
                 EXPORTING
                   it_fieldcatalog = g_t_ifc
                    it_fieldcatalog = g_t_fieldcat
                 IMPORTING
                    ep_table        = dy_table.
ASSIGN dy_table->* TO <dyn_table>.
Create dynamic work area and assign to FS
CREATE DATA dy_line LIKE LINE OF <dyn_table>.
ASSIGN dy_line->* TO <dyn_wa>.
Now this <dyn_table> has fields like idoc no.,creation date ,
segment field 1, segment field 2 etc..Now idoc no.,creation date are static fields from table EDIDC. And segment field 1, segment field 2 etc are dynamic fields from table EDSAPPL.
In my ALV report I am getting the final layout properly but I am unable to move values to corresponding fields in the final layout shown.Please let me know how to populate these fields from different tables.
I tried this way but its not working.
SORT g_t_edid4 BY docnum.
LOOP AT g_t_edidc INTO g_r_edidc.
    READ TABLE g_t_edid4 into g_r_edid4
                     WITH KEY docnum = g_r_edidc-docnum
                                    BINARY SEARCH.
    IF sy-subrc = 0.
      <dyn_wa> = g_r_edid4-sdata.
     MOVE-CORRESPONDING g_r_edid4 to <dyn_wa>.
   CLEAR g_r_edid4.
    ENDIF.
MOVE-CORRESPONDING g_r_edidc to <dyn_wa>.
APPEND <dyn_wa> TO <dyn_table>.

You have to assign each field to field symbol and then assign the value to that field symbol and asssign that field symbol to workarea field symbol.
LOOP AT g_t_edidc INTO g_r_edidc.
READ TABLE g_t_edid4 into g_r_edid4
WITH KEY docnum = g_r_edidc-docnum
BINARY SEARCH.
IF sy-subrc = 0.
ASSIGN COMPONENT 'SDATA' OF STRUCTURE <DYN_WA> TO <DYN_FLD>.
<DYN_FLD> = g_r_edid4-sdata.
" <dyn_wa> = g_r_edid4-sdata.
" Assign each fields like this.
" MOVE-CORRESPONDING g_r_edid4 to <dyn_wa>.
CLEAR g_r_edid4.
ENDIF.
" MOVE-CORRESPONDING g_r_edidc to <dyn_wa>.
APPEND <dyn_wa> TO <dyn_table>.
Regards,
Naimesh Patel

Use of internal table with hearerline in ABAP OO

Hi,
I have a very basic question regarding the use of Internal table with headerline in ABAP OO.
I consider the concept of Internal table with header as one of the most features of ABAP, which is not there in any of the other porgramming languages.
I accept that OO's concept is one of the most powerful and a very good concept. We should also implement OO's concept in ABAP.
But my concern is why in the process of moving to OO's the concept of Internal table with headerline is no more used.
Can any one tell me the main reason for this. Is there any technical reason for this. By this i mean anything to do with memory or effeciency.
Thanx,
Srinivas

Hi Srinivas,
here is something more which i found about the same
follow this link
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
and search for header line.
it says:
Tables with header lines not allowed
Only tables without header lines can be declared in ABAP Objects.
Error message in ABAP Objects if the following syntax is used:
DATA itab TYPE LIKE TABLE OF ... WITH HEADER LINE.
Correct syntax:
DATA: itab TYPE LIKE TABLE OF ... ,
wa LIKE LINE OF itab.
Reason:
It depends on the statement whether the body or header line of a table is accessed. The table name should identify the table uniquely. Programs are easier to read. Tables with header lines do not improve performance.
i hope this will help you.
regards,
Kinshuk
PS mark helpful answers

Query plan changes when query is used in CREATE TABLE AS

We've puzzled by the fact that EXPLAIN PLAN gives a much different output for a SELECT statement than it does when the same statement is used for CREATE TABLE . . . AS SELECT.
The bad part is that the CREATE TABLE version performs very badly, and that's what we want the query for.
Why does this happen? Is there a difference (from the database's point of view) between retrieving a set of rows to display to the user and putting that same set into a new table? Doesn't this make it harder to diagnose and fix query performance problems?
Here's our query:
create table query_test AS
select term, parentTerm, apidb.tab_to_string(cast(collect(trim(to_char(internal)))
                   as apidb.varchartab), ', ') as internal
             from (
                 select distinct ga.organism as term,
                                 ga.species as parentTerm,
                                 tn.taxon_id as internal
                 from apidb.GeneAttributes ga, SRES.TaxonName tn, sres.Taxon t,
                      dots.AaSequence aas, dots.SecondaryStructure ss
                 where ga.organism = tn.name
           and tn.taxon_id = t.taxon_id
                   and t.taxon_id = aas.taxon_id
   and aas.aa_sequence_id = ss.aa_sequence_id
           and t.rank != 'species'
           union
                 select distinct ga.species as term,
                   '' as parentTerm,
                                 ts.taxon_id as internal
                 from apidb.GeneAttributes ga, SRES.TaxonName tn, apidb.taxonSpecies ts,
                      dots.aasequence aas, dots.SecondaryStructure ss
                 where ga.organism = tn.name
                  and tn.taxon_id = ts.taxon_id
                  and ts.taxon_id = aas.taxon_id
                 and aas.aa_sequence_id = ss.aa_sequence_id
   group by term,parentTerm;Without the CREATE TABLE, the plan looks like this:
| Id | Operation                             | Name                      | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | CREATE TABLE STATEMENT                |                           | 2911 | 5986K|       | 18840   (1)| 00:03:47 |
|   1 | LOAD AS SELECT                       | QUERY_TEST                |       |       |       |            |          |
|   2 |   VIEW                                |                           | 2911 | 5986K|       | 18669   (1)| 00:03:45 |
|   3 |    SORT GROUP BY                      |                           | 2911 |   332K|       | 18660   (1)| 00:03:44 |
|   4 |     VIEW                              |                           | 2911 |   332K|       | 18659   (1)| 00:03:44 |
|   5 |      SORT UNIQUE                      |                           | 2911 |   292K|       | 18659   (6)| 00:03:44 |
|   6 |       UNION-ALL                       |                           |       |       |       |            |          |
|* 7 |        HASH JOIN                      |                           | 2907 |   292K| 2160K| 17762   (1)| 00:03:34 |
|   8 |         TABLE ACCESS FULL             | GENEATTRIBUTES10650       | 40957 | 1679K|       |   795   (1)| 00:00:10 |
|* 9 |         HASH JOIN                     |                           | 53794 | 3204K| 1552K| 16675   (1)| 00:03:21 |
|* 10 |          HASH JOIN                    |                           | 37802 | 1107K|       | 12326   (1)| 00:02:28 |
|* 11 |           HASH JOIN                   |                           | 37945 |   629K|       | 10874   (1)| 00:02:11 |
| 12 |            INDEX FAST FULL SCAN       | SECONDARYSTRUCTURE_REVIX9 | 37945 |   222K|       |    33   (0)| 00:00:01 |
| 13 |            INDEX FAST FULL SCAN       | AASEQUENCEIMP_REVIX6      | 7886K|    82M|       | 10816   (1)| 00:02:10 |
|* 14 |           TABLE ACCESS FULL           | TAXON                     |   514K| 6530K|       | 1450   (1)| 00:00:18 |
| 15 |          TABLE ACCESS FULL            | TAXONNAME                 |   760K|    22M|       | 2721   (1)| 00:00:33 |
|* 16 |        HASH JOIN                      |                           |     4 |   380 |       |   886   (1)| 00:00:11 |
| 17 |         NESTED LOOPS                  |                           |   730 | 64970 |       |   852   (1)| 00:00:11 |
|* 18 |          HASH JOIN                    |                           |     1 |    78 |       |   847   (1)| 00:00:11 |
| 19 |           NESTED LOOPS                |                           |       |       |       |            |          |
| 20 |            NESTED LOOPS               |                           |    17 |   612 |       |    51   (0)| 00:00:01 |
| 21 |             TABLE ACCESS FULL         | TAXONSPECIES10646         |    12 |    60 |       |     3   (0)| 00:00:01 |
|* 22 |             INDEX RANGE SCAN          | TAXONNAME_IND01           |     1 |       |       |     2   (0)| 00:00:01 |
| 23 |            TABLE ACCESS BY INDEX ROWID| TAXONNAME                 |     1 |    31 |       |     4   (0)| 00:00:01 |
| 24 |           TABLE ACCESS FULL           | GENEATTRIBUTES10650       | 40957 | 1679K|       |   795   (1)| 00:00:10 |
|* 25 |          INDEX RANGE SCAN             | AASEQUENCEIMP_REVIX6      |   768 | 8448 |       |     5   (0)| 00:00:01 |
| 26 |         INDEX FAST FULL SCAN          | SECONDARYSTRUCTURE_REVIX9 | 37945 |   222K|       |    33   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   7 - access("GA"."ORGANISM"="TN"."NAME")
   9 - access("TN"."TAXON_ID"="T"."TAXON_ID")
10 - access("T"."TAXON_ID"="TAXON_ID")
11 - access("AA_SEQUENCE_ID"="SS"."AA_SEQUENCE_ID")
14 - filter("T"."RANK"<>'species')
16 - access("AA_SEQUENCE_ID"="SS"."AA_SEQUENCE_ID")
18 - access("GA"."ORGANISM"="TN"."NAME")
22 - access("TN"."TAXON_ID"="TS"."TAXON_ID")
25 - access("TS"."TAXON_ID"="TAXON_ID")
46 rows selected.With the CREATE TABLE, the plan for the SELECT alone looks like this:
| Id | Operation                           | Name                      | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                    |                           |     2 |   234 | 1786   (1)| 00:00:22 |
|   1 | SORT GROUP BY                      |                           |     2 |   234 | 1786   (1)| 00:00:22 |
|   2 |   VIEW                              |                           |     2 |   234 | 1785   (1)| 00:00:22 |
|   3 |    SORT UNIQUE                      |                           |     2 |   198 | 1785 (48)| 00:00:22 |
|   4 |     UNION-ALL                       |                           |       |       |            |          |
|* 5 |      HASH JOIN                      |                           |     1 |   103 |   949   (1)| 00:00:12 |
|   6 |       NESTED LOOPS                  |                           |   199 | 19303 |   915   (1)| 00:00:11 |
|   7 |        NESTED LOOPS                 |                           |    13 | 1118 |   850   (1)| 00:00:11 |
|   8 |         NESTED LOOPS                |                           |    13 |   949 |   824   (1)| 00:00:10 |
|   9 |          VIEW                       | VW_DTP_E387155E           |    13 |   546 |   797   (1)| 00:00:10 |
| 10 |           HASH UNIQUE               |                           |    13 |   546 |   797   (1)| 00:00:10 |
| 11 |            TABLE ACCESS FULL        | GENEATTRIBUTES10650       | 40957 | 1679K|   795   (1)| 00:00:10 |
| 12 |          TABLE ACCESS BY INDEX ROWID| TAXONNAME                 |     1 |    31 |     3   (0)| 00:00:01 |
|* 13 |           INDEX RANGE SCAN          | TAXONNAME_IND02           |     1 |       |     2   (0)| 00:00:01 |
|* 14 |         TABLE ACCESS BY INDEX ROWID | TAXON                     |     1 |    13 |     2   (0)| 00:00:01 |
|* 15 |          INDEX UNIQUE SCAN          | PK_TAXON                  |     1 |       |     1   (0)| 00:00:01 |
|* 16 |        INDEX RANGE SCAN             | AASEQUENCEIMP_REVIX6      |    15 |   165 |     5   (0)| 00:00:01 |
| 17 |       INDEX FAST FULL SCAN          | SECONDARYSTRUCTURE_REVIX9 | 37945 |   222K|    33   (0)| 00:00:01 |
| 18 |      NESTED LOOPS                   |                           |     1 |    95 |   834   (1)| 00:00:11 |
| 19 |       NESTED LOOPS                  |                           |     1 |    89 |   833   (1)| 00:00:10 |
|* 20 |        HASH JOIN                    |                           |     1 |    78 |   828   (1)| 00:00:10 |
| 21 |         NESTED LOOPS                |                           |       |       |            |          |
| 22 |          NESTED LOOPS               |                           |    13 |   949 |   824   (1)| 00:00:10 |
| 23 |           VIEW                      | VW_DTP_2AAE9FCE           |    13 |   546 |   797   (1)| 00:00:10 |
| 24 |            HASH UNIQUE              |                           |    13 |   546 |   797   (1)| 00:00:10 |
| 25 |             TABLE ACCESS FULL       | GENEATTRIBUTES10650       | 40957 | 1679K|   795   (1)| 00:00:10 |
|* 26 |           INDEX RANGE SCAN          | TAXONNAME_IND02           |     1 |       |     2   (0)| 00:00:01 |
| 27 |          TABLE ACCESS BY INDEX ROWID| TAXONNAME                 |     1 |    31 |     3   (0)| 00:00:01 |
| 28 |         TABLE ACCESS FULL           | TAXONSPECIES10646         |    12 |    60 |     3   (0)| 00:00:01 |
|* 29 |        INDEX RANGE SCAN             | AASEQUENCEIMP_REVIX6      |   768 | 8448 |     5   (0)| 00:00:01 |
|* 30 |       INDEX RANGE SCAN              | SECONDARYSTRUCTURE_REVIX9 |     1 |     6 |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   5 - access("AA_SEQUENCE_ID"="SS"."AA_SEQUENCE_ID")
13 - access("ITEM_1"="TN"."NAME")
14 - filter("T"."RANK"<>'species')
15 - access("TN"."TAXON_ID"="T"."TAXON_ID")
16 - access("T"."TAXON_ID"="TAXON_ID")
20 - access("TN"."TAXON_ID"="TS"."TAXON_ID")
26 - access("ITEM_1"="TN"."NAME")
29 - access("TS"."TAXON_ID"="TAXON_ID")
30 - access("AA_SEQUENCE_ID"="SS"."AA_SEQUENCE_ID")
50 rows selected.Edited by: JohnI on Jul 18, 2011 2:19 PM
Edited by: JohnI on Jul 18, 2011 2:28 PM

Charles Hooper wrote a series of blog entries on a similar topic some time ago: http://hoopercharles.wordpress.com/2010/12/15/select-statement-is-fast-insert-into-using-the-select-statement-is-brutally-slow-1/ (including a lot of useful comments) and two following articles. I have to confess that I did not read the posts again - but I think you will find some good ideas how to analyze the problem.
Regards
Martin Preiss

Use of Association Tables in Place of FK's -- O/R Mapping

We are currently in the process of redesigning one of our systems following an OO model to be implemented in Java. Our current Oracle database is 8.1.7. We care coding sql in JDBC directly without the use of mapping tools. My role in the project is a jr. schema dba.
The oo designer on our team objects to holding foreign key attributes in the Java classes when (form the object model's perspective) they aren't need (i.e. using collections will indicate parent-child relationships).
To get around the "foreign key problem" the oo designer is pushing for the use of "association tables" in the database to replace foreign key relationships. The designer and other members of the team (the sr. schema dba) cite literature on O/R mapping which suggests that this technique is a valid and viable approach.
So as a simple example...
DEP EMP
=======          =======
# dep_no     # emp_no
dep_name     dep_no
          emp_name
Becomes...
DEP EMP          A_DEP_EMP
=======          =======     =========
# dep_no     # emp_no     # dep_no
dep_name     emp_name     # emp_no
Where A_DEP_EMP is the association table showing the relationship between department and employee.
To me it seems like we are making poor and unnecessary database design decisions to support the object model. My objections to this association table approach is that we are failing to use the inherent strengths of the a relational database:
1) Both the dep and emp must exist before the association is built (assuming the association has FK's to the DEP and EMP tables) -- and yes I'm aware delaying the enforcement of FKs until commit time is an option
2) The model does not protect against inserting orphaned emps into the EMP table (assuming we'd want to protect against this)
3) The association table indicates a N:M cardinality. Assuming the design calls for a 1:M cardinality a UK on the emp_no column in the association table would be required. When I brought this up, the sr. schema dba raised concerns about the overhead of the UK and suggested that the application would be responsible for enforcing the cardinality requirements.
The alternative that seems more appealing is managing the FK details in a persistence layer of the Java classes (currently the notion of separate view and entity objects is absent in our design -- the database interface is directly in each low-level java class).
If i am correct in my understanding of Oracle's implementation of BC4J the foreign keys are handled in the persistence layer (view object) with out the need for actively maintaining them in the entity Object. Other O/R mapping models also seem to suggest that this is the way to go (e.g. Martin Fowler's recommendations http://www.martinfowler.com/isa/).
So my question for the community at large:
- Which approach would you use?
- Has anyone been working with association tables in place of foreign keys? If so what are your experiences?
- am i off-base with my objections?
any feedback / comments much appreciated

Martin,
I have seen these kind of discussions over and over again and now you happen to be right in the middle of one. Without going into technical details some statements that might help:
1) object model designers and relational model designers will NEVER 'agree' since the techniques used are, by nature, too different (they solve different problems, which is fine, but when you start to talk about them they give problems)
2) my experience is that they do not have to 'agree', as long as they can 'work alongside eachother'. You are not there to tell the object designers how to do their work the same way they are not there to tell you how to do your job.
3) as a senior DBA, I regard it my primary task to enforce regulations that will make the data stored as meaningfull and correct as possible. If I'm following relational principles to do so, I will use all of them where I find them applicable regardless how that data is used later on. Any suggestion by any person that undermines this principle will not get implemented. Exceptions (<0.1%) not taken into account. Also, there is a 'political correct' way of telling this and a 'bold' way.
4) choose the 'political correct' one since it will save you a lot of stress :)
5) if you violate rule 3, and shit happens, you will be held accountable (and rightfully so).
6) if you have a more senior person telling you what to do, do it, but state your concerns very clearly in an email and save that mail + reply somewhere safe for future discussions. Refer to this if shit happens and you are, unrightfully so, held accountable.
7) as a DBA, never trust application logic to enforce data integrity. It is your job, not the application developer's and you have the facilities to do so much easier than the app dev. Application developers don't have a primary task of testing data integrity, if it looks ok on the screen they pass their tests. you on the other hand perform special tests they don't. This is your additional value to the project.
8) in oracle 8i and above I found the use of views and 'in stead of'-triggers very usefull for mimicing objects. Object designers/developers think they get simple tables they can map objects to and underneatch you yourself check everything is ok. The disadvantage of this is that you need to do some extra work not easily accounted for and might run into some performance issues, but that is your challange as you want to become a senior DBA ;). The advantage is that the discussion is over :) and reporting and other, none object applications can interface more easily (which might be an actual design decisive argument, I've used it successfully multiple times).
9) try to stay away from discussions of how things are done best between the two methods and why one method 'is better' than the other. Try to find a workable solution that will violate the least of the two designing principles and implement that.
A lot is dependent on your project and it might be that in your case these senior people are quite right in their suggestions, but I've found that the above 'rules' work most of the time for me. I hope they at least give you something to think about. From what I read from your post, it sounds like you know the technical pros and cons but you have a tough time communicating to your peers. Perhaps these rules help a bit.
Success,
Lennert
We are currently in the process of redesigning one of our systems following an OO model to be implemented in Java. Our current Oracle database is 8.1.7. We care coding sql in JDBC directly without the use of mapping tools. My role in the project is a jr. schema dba.
The oo designer on our team objects to holding foreign key attributes in the Java classes when (form the object model's perspective) they aren't need (i.e. using collections will indicate parent-child relationships).
To get around the "foreign key problem" the oo designer is pushing for the use of "association tables" in the database to replace foreign key relationships. The designer and other members of the team (the sr. schema dba) cite literature on O/R mapping which suggests that this technique is a valid and viable approach.
So as a simple example...
DEP EMP
=======          =======
# dep_no     # emp_no
dep_name     dep_no
          emp_name
Becomes...
DEP EMP          A_DEP_EMP
=======          =======     =========
# dep_no     # emp_no     # dep_no
dep_name     emp_name     # emp_no
Where A_DEP_EMP is the association table showing the relationship between department and employee.
To me it seems like we are making poor and unnecessary database design decisions to support the object model. My objections to this association table approach is that we are failing to use the inherent strengths of the a relational database:
1) Both the dep and emp must exist before the association is built (assuming the association has FK's to the DEP and EMP tables) -- and yes I'm aware delaying the enforcement of FKs until commit time is an option
2) The model does not protect against inserting orphaned emps into the EMP table (assuming we'd want to protect against this)
3) The association table indicates a N:M cardinality. Assuming the design calls for a 1:M cardinality a UK on the emp_no column in the association table would be required. When I brought this up, the sr. schema dba raised concerns about the overhead of the UK and suggested that the application would be responsible for enforcing the cardinality requirements.
The alternative that seems more appealing is managing the FK details in a persistence layer of the Java classes (currently the notion of separate view and entity objects is absent in our design -- the database interface is directly in each low-level java class).
If i am correct in my understanding of Oracle's implementation of BC4J the foreign keys are handled in the persistence layer (view object) with out the need for actively maintaining them in the entity Object. Other O/R mapping models also seem to suggest that this is the way to go (e.g. Martin Fowler's recommendations http://www.martinfowler.com/isa/).
So my question for the community at large:
- Which approach would you use?
- Has anyone been working with association tables in place of foreign keys? If so what are your experiences?
- am i off-base with my objections?
any feedback / comments much appreciated

Use of salrt table in XI

Similar Messages

Maybe you are looking for