First, we create a tablespace to hold the historical data. This keeps the audit data separate from the live data.
In the late 1970s, the world of data was rigid and complex, with data locked in "hierarchical" systems that were difficult to change. In 1977, Larry Ellison and his team set out to change this, inspired by an IBM paper on a more flexible "relational" model. By 1979, they released , the first commercially available SQL-based relational database.
This example demonstrates a specific capability of : Flashback Data Archive (FDA) . This feature allows you to track historical data changes over long periods for compliance and auditing without cluttering your main application tables.
| Feature | Standard Edition 2 (SE2) | Enterprise Edition (EE) | | :--- | :--- | :--- | | Max CPU Sockets | 2 sockets (unlimited cores per socket) | Unlimited | | Memory | Limited by OS/hardware | Unlimited | | RAC Support | Yes (limited to 2 nodes) | Yes (unlimited nodes) | | Data Guard | No (only snapshot standby) | Yes (Active Data Guard) | | In-Memory | No | Yes (optional extra cost) | | Partitioning | No | Yes |
-- Create the live table CREATE TABLE transactions ( txn_id NUMBER PRIMARY KEY, account_id NUMBER, amount NUMBER(15,2), txn_date TIMESTAMP DEFAULT SYSTIMESTAMP, status VARCHAR2(20) );
Unlike SE2, which is limited to 2-socket servers and 16 vCPUs in certain cloud environments, EE can scale to the largest SMP servers and clusters.
We define the retention policy (5 years).
Note: In Enterprise Edition, you can also enable optimization so that fetching history does not impact current transaction performance.
A password will be e-mailed to you