Materialized views can be used to cache the results from queries that would normally be very demanding on a database. This is much different than a regular view which doesn’t actually store any data. A regular view only stores a query that will be executed against the base table, while a materialized view will actually store the results from a query that was executed on the base table. Once the materialized is created, the data can be refreshed in two ways: complete or fast. In this blog, I will discuss the use of a complete refresh, and I will discuss the use of a fast refresh in the next blog.
In the last article, we examined a common, manual method for enabling auditing on tables. With Oracle Database 11g, Total Recall is a built-in product that allows the same functionality. Total Recall stores the undo information for any audited table in a separate tablespace using flashback archiving. First, a privileged user needs to create a flashback archive:
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: