Answer Posted / s

Simple tablespaces stores the rows for all the tables and
they are interleaved with one another.

Segmented tablespaces, tables are stored in equal sized
segments and a segment contains rows from one table.

Partitioned tablespace, only one table can be defined and
rows are spread across partitions.

SET is the ANSI standard for variable assignment, SELECT is not. SET can only assign one variable at a time, SELECT can make multiple assignments at once. If assigning from a query, SET can only assign a scalar value. If the query returns multiple values/rows then SET will raise an error. SELECT will assign one of the values to the variable and hide the fact that multiple values were returned (so you'd likely never know why something was going wrong elsewhere - have fun troubleshooting that one) When assigning from a query if there is no value returned then SET will assign NULL, where SELECT will not make the assignment at all (so the variable will not be changed from it's previous value) As far as speed differences - there are no direct differences between SET and SELECT. However SELECT's ability to make multiple assignments in one shot does give it a slight speed advantage over SET.

2682

---

What is the use of db2?

1061

---

If I have a view which is a join of two or more tables, can this view be updateable?

1139

---

What is the difference between drop table and delete table?

1220

---

How can you count the number of rows from a table tab?

1096

---

What is package in db2 mainframe?

994

---

What are the 2 sqlcodes that are returned?

1196

---

What is concurrency?

1243

---

What is copy pending status in db2?

1129

---

Where do you specify them?

1292

---

Give a brief description of db2 isolation levels?

1077

---

What is isolation level in db2?

1017

---

What is cobol db2?

1007

---

How do I add a column to an existing table in db2?

1037

---

What are the various data types available in db2?

1103

---