Answer / vivek

Global Temporary tables are session dependant tables which
could be used as temporary storage for calculations, sorting
etc. What I mean by Session dependant is, the data being
stored in the Global Temporary table is not written into the
database or stored anywhere. Once the session ends (in which
the Global Temporary table is used), the data also vanishes.



However the structure would still be available even after
the Session is logged out. Also, the structure is available
to other sessions even when one session is using it, but not
the data. i.e multiple sessions could use the same Global
Temporary table without interfering the data. Each session
could insert/update/delete their own data into the same
Global Temporary table as if the table is available to only
that session. Any data inserted in one session is not
available to another.



Now, why do we need Global Temporary tables? Well, imagine a
requirement where you need to fetch some data from the
database, do some kind of calculations, aggregations and
provide the Result Set (many records) to a Front End. Again,
in the Front End, you need to fetch the Result set may
times, for some purpose. Then you could make use of the
Global Temporary table. Until the user gets disconnected
from that Database session, the data is available for him in
the memory.

Answer / subbu

Global temporary tables belongs to that session only

create global temporary table test_gbl
( l_number_no number,
l_char_vc varchar2(100)
) [on commit delete rows]

ON COMMIT DELETE ROWS:- It's a default one
If any commit will issued that total data of a table will
losses. But table is exit

To overcome this we have option
ON COMMIT PRESERVE ROWS:-
means, If commit will issue the data of a table willn't loss
up to end of the session. Is session ends the data will losses.

Regards
Subbu

Answer / subbu

Global temporary tables belongs to that session only

create global temporary table test_gbl
( l_number_no number,
l_char_vc varchar2(100)
) [on commit delete rows]

ON COMMIT DELETE ROWS:- It's a default one
If any commit will issued that total data of a table will
losses. But table is exit

To overcome this we have option
ON COMMIT PRESERVE ROWS:-
means, If commit will issue the data of a table willn't loss
up to end of the session. Is session ends the data will losses.

Regards
Subbu

What do you understand by exception handling in pl/sql?

0 Answers  

---

What are sql built in functions?

0 Answers  

---

What is sql resultset?

0 Answers  

---

Which is better varchar or nvarchar?

0 Answers  

---

after tell procedure whole code he asked can i write the same way in a function

3 Answers  

---

Why cross join is used?

0 Answers  

---

I have a small PL/SQL Block assume in this way begin select * from emp where empno=100; exception when others then <Some Messages> when no_data_found then <Some Messages> when too_many_rows then <Some Messages> end; The question which he asked was whether this block will get executed normally or it will throw error ? If errored out then what is the reason for the error ? Could anybody please help me ? Regards Nakul Venkataraman

3 Answers   Satyam,

---

Explain 3 basic parts of a trigger.

0 Answers  

---

When is the update_statistics command used?

0 Answers  

---

How do I upgrade sql?

0 Answers  

---

what is the difference between delete and truncate statement in sql? : Sql dba

0 Answers  

---

How do I find sql profiler?

0 Answers  

---