Answer / narasa

compression is process. in this data will go to the F table
to E table on Cube by deleting the requests and make a
Single request no. it will save a space and data redundency.

if its wrong send mail correct ans to me.

Answer / sapbhai

When the requests are compressed all the request ids are lost (set to NULL) and you would not be able to select/delete the data by request id. The data in the F fact table (uncompressed fact table) is moved to E fact table (compressed fact table). Compressed data occupies less space in many cases and thus a performance boost.

Answer / guest

This is the process by which we delete the request ids.
this saves space

Answer / siva

it is used for to delete the request ids and save the space
once we compress the data moves from f table to e table.

If we want to see the compress data, go to se11
give /bic/e<cubename> we can find out here.

What are the Oracle specific tuning should be done?

0 Answers  

---

How we do the sd and mm configuration for bw?

0 Answers  

---

Describe a opening balance?

0 Answers  

---

What is the licensing requirement you should be aware of?

0 Answers  

---

How is archiving advantageous?

1 Answers  

---

What are the advantages of new LO extraction?

0 Answers  

---

List the tools to monitor overall query performance.

0 Answers  

---

What is the use of BW statistics?

1 Answers  

---

What is a number range object?

0 Answers  

---

Describe your experience with the design and implementation of standard & custom infocubes.

0 Answers  

---

HOW TO SUPRESS TEXT DATA WHILE LOADING MASTER DATA? HOW TO LOAD MASTER DATA WITH OUT CREATING INFOPACKAGE?

1 Answers  

---

When you compressed multiple requests, how would you know which had ?marker update? enabled or not?

0 Answers  

---