Hi,
I have a hold file with multiple rows and I need to insert the rows to a table in database using SQL pass thru via scheduled report every week.

Earlier I tried using just one row with all values in the INSERT statement and it works but how to insert multiple rows from a hold file to a table(similar toe ETL)? Also the table has WF_ID as the primary key.

Please let me know. Thanks in advance.

RK

This message has been edited. Last edited by: FP Mod Chuck,

Have you considered HOLD FORMAT SQLORA or whatever RDBMS you want to populate? It seems a lot less effort than what you describe.

HOLD FORMAT to RDBMS creates a new table.
I need to load it to the existing table with new rows based on the report date. Also increment the auto generate the primary key.

Thank you
RK

Do you need to use SQL pass thru ?

You could use MODIFY (Depending on the content like clobs and blobs)

If your database supports creating multiple VALUES rows, you can generate the SQL for that.

For example:

INSERT INTO CAR (COUNTRY, CAR)
VALUES
  ('JAPAN', 'MAZDA')
, ('ITALY', 'FIAT')
, ('FRANCE', 'PEUGEOT')
, ('FRANCE', 'CITROEN');

The lines under VALUES is what you would generate the code for.

To add to Wep's suggestion

 -DEFAULTH &LOOP_CNTR = 0;
-DEFAULTH &CAR = '';
-DEFAULTH &COUNTRY = '';
-DEFAULTH &MODEL = '';

TABLE FILE CAR
PRINT
CAR
COUNTRY
MODEL 
ON TABLE SAVE AS COL_VALUES
END
-RUN
-SET &LOOP_CNTR = &LINES;
-REPEAT :Fetch_Data &LOOP_CNTR TIMES

-READ COL_VALUES  &CAR.A16 &COUNTRY.A10 &MODEL.A20

-TYPE VALUES ARE &CAR &COUNTRY &MODEL
-*Have your sql statement here
 INSERT INTO CAR (COUNTRY, CAR, MODEL)
 VALUES
('&COUNTRY', '&CAR','&MODEL');

-:Fetch_Data 

How many rows do you want to insert? Looping with insert statements is limited, MODIFY is the best way to properly insert data in existing tables.

Actually, that looks like a great task for my new favourite WebFOCUS function: PUTDDREC

-SET &LIST = 'INSLIST';
FILEDEF &LIST DISK INSLIST.ftm

TABLE FILE CAR
PRINT
  COMPUTE COMMA/A1 = IF LAST COUNTRY EQ '' THEN ' ' ELSE ','; NOPRINT
  COMPUTE INSTUPLE/A256 = COMMA | '(''' || COUNTRY || ''', ''' || CAR || ''', ''' || MODEL || ''')'; NOPRINT
  COMPUTE RESULT/I1 = PUTDDREC('&LIST', &LIST.LENGTH, INSTUPLE, ARGLEN(256, INSTUPLE, 'I3'), RESULT); NOPRINT

-* Other useful stuff you may want to hold unrelated to the insert list

BY COUNTRY NOPRINT
BY CAR NOPRINT
BY MODEL NOPRINT
ON TABLE HOLD
END
-RUN

SQL SQLMSS PREPARE SQLOUT FOR
INSERT INTO CAR (COUNTRY, CAR, MODEL)
VALUES
-INCLUDE INSLIST.ftm
;
END

quote:

PUTDDREC

quote:

Originally posted by Frans:
How many rows do you want to insert? Looping with insert statements is limited, MODIFY is the best way to properly insert data in existing tables.

Every week 200 to 300 rows.

This helps, I will try and update you.:FETCH_DATA is the webfocus command? What does it do?

Thank you

quote:

Originally posted by Addy:
To add to Wep's suggestion

 -DEFAULTH &LOOP_CNTR = 0;
-DEFAULTH &CAR = '';
-DEFAULTH &COUNTRY = '';
-DEFAULTH &MODEL = '';

TABLE FILE CAR
PRINT
CAR
COUNTRY
MODEL 
ON TABLE SAVE AS COL_VALUES
END
-RUN
-SET &LOOP_CNTR = &LINES;
-REPEAT :Fetch_Data &LOOP_CNTR TIMES

-READ COL_VALUES  &CAR.A16 &COUNTRY.A10 &MODEL.A20

-TYPE VALUES ARE &CAR &COUNTRY &MODEL
-*Have your sql statement here
 INSERT INTO CAR (COUNTRY, CAR, MODEL)
 VALUES
('&COUNTRY', '&CAR','&MODEL');

-:Fetch_Data 

Hi Riya,
:Fetch_data is a label that I created so that I can loop throught a segment.

You can call it whatever you want. I generally create my labels starting with : but it is not a compulsion.

have a look at following documentation

Looping in WF
Branching

Depending on the volume I use SQL Insert, the SQL Loader, and MODIFY. For just a few hundred records, I'd use MODIFY and if all you are doing is inserting then make sure to use "SET SQL LOADONLY" right after the MODIFY statement. This tell MODIFY that all you are doing is loading and it cuts the I/O in half. Without it, MODIFY doesn't know if you are loading, updating or both. As a result, MODIFY will do an unnecessary SQL SELECT first to see if the row exist then do the SQL INSERT when it doesn't. You can see this if you turn traces on.

Riya, Using BabakNYC's idea.

Do your

 
HOLD FORMAT SQLORA
 

into a temp table (say TEMP_DATA)

Then run an insert into your table using the temp table.

Insert into MY_TABLE (col1,col2)
Select a.col1 AS col1, 
a.col2 AS col2
FROM TEMP_DATA

Fernando

Fernando, thats a great idea.