NOTE: SUBJECT DATABASE Managment system

There is/are table(s) having more than one FK (which are neither PK nor part of PK) True/False True Q: Relationship Line lies between having cardinality & respectively. & entities: modularity. Between: Salesrep & Order, Cardinality Q: Relationship Write lies between having cardinality & respectively. & entities; modularity, Between: Purchase & Product, Cardinal There is no table having composite PK (True/False) False Q: Relationship Have lies between having cardinality & respectively. entities: modularity, Between: Customer & Invoice, Cardinal Only FKs (which are nither PK's or part of PKS) are Final Moct Exam Ims.dsu.edu.pk/mod/quiz/attempt.php?attempt=24551&cmid=219 DSU LMS F There is only one recovery protocol available in Databases, (T/F) Incremental log with immediate update technique. Transaction log is used in N Incremental log with immediate update and incremental log with deffered update are same (Y/N) only the portion After system failure, transaction 106 need (eg.: redo/undo/NA) (eg after/before/NA) the last check point Note: NA when there is no question/sense of saying after or before 431 to 405 Only to answer this question, assume the system was crashed al TRL_ID: 457: Now answer that, transaction 106 need undorollback from TRL_ID to in reverse order 419 to 405 only the portion (eg. 1 After system failure transaction 155 need (e.g. redo/undo/NA) after before/NA) the last check point. Note: NA when there is no questionisense of saying after or before = 419 to 405 ESSE Afler system failure, what should we do for transaction 101(eg. Nothing Redo Undo, etc.) Nothing Recovery Techniques are implemented in Database Systems by the DBMS Y Only to answer this question assume the system was crashed at TRL_ID: 528 and rollback was issued at TRL_ID 457. Now answer that what will be done from the following (Select any one from 1-5) 1. Both will be undone in simple from TRL_ID: 525 to 405. 2 Only Transaction 106 will be undone from TRL_ID 431 to 405 action.haudoit Type here to search O e WE Q: Relationship Have lies between having cardinality & respectively. & entities: modularity Between: Customer & Invoice, Cardinal Only FKs (which are nither PK's or part of PKs) are contained in following tables Product, Invoice there are total no of tables in my solution 6 Q: Relationship Supply lies between & entities; having cardinality & modularity, respectively. Between: Salesrep & Invoice, Cardinalit Next page 419 to 405 Only to answer this question, assume the system was crashed at TRL_ID: 457: Now answer that, transaction 106 need undo/rollback from TRL ID to in reverse order. only the portion (e.g. 419 to 405 1. After system failure, transaction 155 need (eg.: redo/undo/NA) after before/NA) the last check point Note: NA when there is no question/sense of saying after or before. Nothing After system failure, what should we do for transaction 101 (e.g.: Nothing, Redo, Undo, etc.) Y Recovery Techniques are implemented in Database Systems by the DBMS ES 3 Only to answer this question, assume the system was crashed at TRL_ID: 528 and rollback was issued at TRL ID 457. Now answer that what will be done from the following (Select any one from 1-5): 1. Both will be undone in simple from TRL_ID: 525 to 405. 2. Only Transaction 106 will be undone from TRL_ID:431 to 405 3. Only Transaction 106 will be undone from TRL_ID: 419 to 405 4. Nothing will be done because because both was going after the last check point. 5. None of these technique works when transaction committed and does nothing otherwise Developers (eg.: Oracle, IBM) Next page Type here to search hp There is/are table(s) having more than one FK (which are neither PK nor part of PK) True/False True Q: Relationship Line lies between having cardinality & respectively. & entities: modularity. Between: Salesrep & Order, Cardinality Q: Relationship Write lies between having cardinality & respectively. & entities; modularity, Between: Purchase & Product, Cardinal There is no table having composite PK (True/False) False Q: Relationship Have lies between having cardinality & respectively. entities: modularity, Between: Customer & Invoice, Cardinal Only FKs (which are nither PK's or part of PKS) are Final Moct Exam Ims.dsu.edu.pk/mod/quiz/attempt.php?attempt=24551&cmid=219 DSU LMS F There is only one recovery protocol available in Databases, (T/F) Incremental log with immediate update technique. Transaction log is used in N Incremental log with immediate update and incremental log with deffered update are same (Y/N) only the portion After system failure, transaction 106 need (eg.: redo/undo/NA) (eg after/before/NA) the last check point Note: NA when there is no question/sense of saying after or before 431 to 405 Only to answer this question, assume the system was crashed al TRL_ID: 457: Now answer that, transaction 106 need undorollback from TRL_ID to in reverse order 419 to 405 only the portion (eg. 1 After system failure transaction 155 need (e.g. redo/undo/NA) after before/NA) the last check point. Note: NA when there is no questionisense of saying after or before = 419 to 405 ESSE Afler system failure, what should we do for transaction 101(eg. Nothing Redo Undo, etc.) Nothing Recovery Techniques are implemented in Database Systems by the DBMS Y Only to answer this question assume the system was crashed at TRL_ID: 528 and rollback was issued at TRL_ID 457. Now answer that what will be done from the following (Select any one from 1-5) 1. Both will be undone in simple from TRL_ID: 525 to 405. 2 Only Transaction 106 will be undone from TRL_ID 431 to 405 action.haudoit Type here to search O e WE Q: Relationship Have lies between having cardinality & respectively. & entities: modularity Between: Customer & Invoice, Cardinal Only FKs (which are nither PK's or part of PKs) are contained in following tables Product, Invoice there are total no of tables in my solution 6 Q: Relationship Supply lies between & entities; having cardinality & modularity, respectively. Between: Salesrep & Invoice, Cardinalit Next page 419 to 405 Only to answer this question, assume the system was crashed at TRL_ID: 457: Now answer that, transaction 106 need undo/rollback from TRL ID to in reverse order. only the portion (e.g. 419 to 405 1. After system failure, transaction 155 need (eg.: redo/undo/NA) after before/NA) the last check point Note: NA when there is no question/sense of saying after or before. Nothing After system failure, what should we do for transaction 101 (e.g.: Nothing, Redo, Undo, etc.) Y Recovery Techniques are implemented in Database Systems by the DBMS ES 3 Only to answer this question, assume the system was crashed at TRL_ID: 528 and rollback was issued at TRL ID 457. Now answer that what will be done from the following (Select any one from 1-5): 1. Both will be undone in simple from TRL_ID: 525 to 405. 2. Only Transaction 106 will be undone from TRL_ID:431 to 405 3. Only Transaction 106 will be undone from TRL_ID: 419 to 405 4. Nothing will be done because because both was going after the last check point. 5. None of these technique works when transaction committed and does nothing otherwise Developers (eg.: Oracle, IBM) Next page Type here to search hp