With ever-changing regulatory and compliance requirements, auditing is becoming more important than ever. In this article, we will look at a common-method of enabling auditing within Oracle along with its benefits and drawbacks. In the next article, we will look at a new Oracle solution for auditing.
In order to move a partitioned table to a different tablespace, each partitioned has to be moved. This can be accomplished two ways: manually moving each partitioned or writing a procedure that will loop through each partition and move it. I will discuss how to write a procedure to take care of this task. First, a partitioned table needs to be created and have some values inserted into it. This table is created in the HR schema and partitioned by range:
The last blog, here, discussed different single-level partitioning strategies. This blog will explain strategies to make non-partitioned tables partitioned tables. The objects created will be stored in the HR schema. First, a table needs to be created (this is the same table that was created in the last blog) and a unique index will be put on the column CUSTOMER_ID:
Partitioning tables is a great way to improve the performance and manageability of a table. Sometimes, non-partitioned tables are created that don’t contain much data, but over time the table becomes largely populated. Partitions can be used to manage the proliferation of data in the table. Common single-level partitioning strategies include list partitioning, range partitioning, and hash partitioning. Each partitioning strategy has its own advantages and disadvantages.
Oracle has introduced a new SQL operator in 11g called PIVOT. The PIVOT operator allows query results to be presented in pivot form. Oracle stores data in a manner that is optimized for performance. Sometimes, this makes the data hard to read. Using the PIVOT operator allows the data to be displayed in a more readable and understandable format. The basic syntax for using the PIVOT operator is: