Overall Satisfaction with Oracle Database
Oracle Database is being used in the areas of data warehousing and transaction processing across the whole organization. The business problems it addresses are various log data collection, search engine marketing, and website content optimization. In addition it is used to cleanse, aggregate, load and transform data in the data warehouse, with the data eventually consumed by data analysts and data scientists.
- Maintain data integrity: with database supplied primary/unique keys and referential integrity constraints, data integrity is well-maintained in a highly efficient manner. More over, oracle database enforces transaction integrity and read consistency, and it is extremely rare to have data corruption.
- Versatility and flexibility in usage: Oracle is very versatile and has many capabilities that allow for a great variety of usage and creativity. Most of the real life business use cases can be addressed by it, and one just needs to know how to better take advantage of it.
- Rock-solid foundation and exciting new features: Oracle database has come a long way (created in the mid to late 1970s), and evolved to be the best relational database platform. It has also incorporated many new features over the years, either inside the database engine itself or through add-on options/products. It has a strong life even faced with the new-age challenges such as big data analytics.
- It would be nice to have schema-based privilege grants. Currently, the object privileges are granted either per individual objects (very small knife), or on all objects (very big knife). We need something in between: schema-based privilege grants with the ability to cover new objects owned by a particular schema after the grant. For example: one could use "grant select on all tables of A to B;".
- It may be nice to have the ability to issue commit on behave of another session for its completed but uncommitted transactions. Imagine a scenario that one session issues an update on a table, and after some time the update is completed but the person doesn't commit. The table remains to be locked by the session. Another session needs to update on the same rows after the prior session's update, but it has to wait or kill the other session. Killing the other session means rolling back that session's transaction and losing all of its effort. In this case, if we want to preserve the other session's update, it would be nice to commit on behave of that session (instead of simply killing the session and losing its transaction), and then do our update.
- The use of Oracle Database has improved overall availability, performance, and the capabilities of the business systems, and it has a positive impact on ROI.
- Oracle has the reputation of being expensive. If not planned, sized, and estimated appropriately, one could over spend on things that are not necessary. That will inevitably result in a negative impact on ROI.
- Think about long term, and the availability of people's skill sets within the organization, and the skills accessible outside. Use the right tools for the jobs.
Oracle database is well suited for many situations, even the ones that people think they might need "revolutionary" new tools. It is amazing how many concepts are already implemented but they are re-invented again and again. For example, a lot of business cases involves quick key-value look ups. In an attempt to speed that up with massive amount of data, people often resort to "new" technologies such as "schema-less" key/value database systems. Actually, a lot of these cases can be implemented with Oracle database's Index-Organized Table (IOT). There are some other scenarios that people want to incorporate object-oriented features in the database. While there are specialized databases that employ object storage and implementation, oracle has long had object-relational features (such as nested tables and custom types) and can accommodate most, if not all, of the use cases.
Using Oracle Database
Like to use
Quick to learn
Feel confident using
- Data manipulation and query
- Data processing and transformation
- Loading data into the database
- Unload massive amount of data out of the database
- Some analytics queries and functions
- Monolithic nature of the database storage layer