Which two are facets of performance planning that should always be considered or implemented for an Oracle Database environment? (Choose two.)
Which two are facets of performance planning that should always be considered or implemented for an Oracle Database environment? (Choose two.)
In an Oracle Database environment, it's essential to consider both the physical data model and the configuration of storage arrays as facets of performance planning. The physical data model involves the design and organization of the database's physical storage, which can significantly impact performance through table partitioning, indexing, and materialized views. The configuration of storage arrays pertains to optimizing the storage hardware settings to ensure efficient data retrieval and storage operations, which is crucial for performance optimization. These facets directly influence the I/O performance and the overall efficiency of the database system.
a,b and c are options to enforce data integrity not to speed up queries, i think the correct answers are d and e. if we have a good physical data model in an good storage array configuration we can think of good performance.
...and all constraints have a cost in terms of performance (index update and delete, checks included, etc.) to be managed by the instance itself.
A. defining primary keys for all tables to speed up all queries B. using check constraints to speed up updates C. defining foreign keys for all tables to speed up joins D. the physical data model E. the configuration of storage arrays >> I believe D & E. D - is to do with design the tablespace, partitions etc.. E - is to do with storage layout, that RAID levels e.g. 5 to keep data with high read IO. 1+0 for better write.
A, if you think about warehouse table, not all tables are going to have primary key column ( to save the storage).
DE if physcal model is about ram, cpu, os blocks, hba, switch etc
https://docs.oracle.com/en/database/oracle/oracle-database/19/tgdba/IO-configuration-and-design.html#GUID-96CEF863-67AC-47BE-8834-8AB42864FC6E A good physical model will consider A, B and C options.
What is Oracle data model? The Physical Data Model of the Oracle Communications Data Model is the physical manifestation of the logical data model into database tables and relationships (or foreign key constraints). Partitions, indexes, and Materialized Views have been added to aid performance. so : D and E
I think it's DE Not ABC, since it all of them are a part of D.
"However, it is possible to make a sensible start by building indexes that enforce primary key constraints and indexes on known access patterns, such as a person's name." "I/O Subsystem The I/O subsystem can vary between the hard disk on a client PC and high performance disk arrays. Disk arrays can perform thousands of I/Os each second and provide availability through redundancy in terms of multiple I/O paths and hot pluggable mirrored disks. " So I think A-E are quite viable answers after all, especially because the question asks what facet you should always "consider", which doesn't mean you should necessarily implement them all blindly. From: https://docs.oracle.com/cd/B28359_01/server.111/b28274/design.htm#CJHCJIDB
A and D define primary key will create index which will speed up queries
correct answers are d and e
DE correct
D, E. As stated, not all tables will have a, b, and c. Per https://docs.oracle.com/en/database/oracle/oracle-database/19/tgdba/IO-configuration-and-design.html#GUID-96CEF863-67AC-47BE-8834-8AB42864FC6E: Every Oracle database reads or writes data on disk, thus generating disk I/O. The performance of many software applications is inherently limited by disk I/O. Applications that spend majority of their CPU time waiting for I/O activity to complete are said to be I/O-bound. Additionally, a solid physical model will map out where and what is needed: The Physical Data Model of the Oracle Communications Data Model is the physical manifestation of the logical data model into database tables and relationships (or foreign key constraints). Partitions, indexes, and Materialized Views have been added to aid performance. (https://docs.oracle.com/cd/E84720_01/CDMRF/physical-data-model.htm#CDMRF717)
DE i think
Primary Keys won't spenden up all queries
A,D Refer to the question: "should always be considered or implemented" so E is correct but not always considered it due to company budget
A,E is correct: C - defining foreign keys not include an automatic index creation, therefore the foreign key can't have an index D- physical data model is a graphical schemas of table and relation
for sure C D is correct
What does it mean more exactly "the physical data model"? DB Block? Better sounds the answer with "the configuration of storage arrays " than "the physical data model " :)