NAME

Question types


Start with


Question limit

of 123 available terms

Print test

123 Multiple choice questions

  1. True
  2. IN_STATE_STUDENT
  3. candidate
  4. True
  5. Sample data can reverse database implementation errors
  6. Systables
  7. PartNum
  8. attributes
  9. Entity
  10. entry-relationship diagram
  11. Supertype
  12. system-generated; usually hidden from users
    Also called a synthetic key
  13. Create two new relation
  14. UPDATE
  15. foreign key
  16. AS
  17. LIKE
  18. True
  19. *
  20. Descriptor
  21. Well-Structured
  22. True
  23. Insertion anomaly
    Deletion anomaly
    Modification anomaly
    (All the above)
  24. A -> B
  25. are drawn as diamonds with lines connecting the entities involved in relationships
  26. data Independence
  27. repeating groups
  28. legal-values
  29. CREATE INDEX
  30. data must follow in the database
  31. Enterprise Key
  32. Primary
  33. True
  34. Determinant
  35. depends on another entity for its own existence
  36. False
  37. SELECT CustomerNum, CustomerName, CreditLimit, Balance FROM Customer WHERE CreditLimit>Balance;
  38. Attribute
  39. Well-Structured Relation
  40. redundancy
  41. determinant
  42. partial dependencies
  43. null
  44. drawn as rectangles
  45. simplest implementation is to treat it as a one-to-many relationship
  46. SELECT TripName
    FROM Trip
    WHERE State !='NH';
  47. Data independence
  48. set of requirements necessary to support operations of a particular database user
  49. Security
  50. Each attribute has a unique name
    No two rows in a relation are identical
    There are no multivalued attributes in a relation
    (All the above)
  51. SMALLINT
  52. Attribute
  53. Data accessibility
    Response times
    Security
  54. foreign key
  55. include primary key of the "one" table as a foreign key in the "many" table
  56. supports all user views encountered during design process
  57. existence of one entity depends on the existence of another related entity
  58. Integrity
  59. Partial
  60. False
  61. write both the table name and the column name, separated by a period
  62. : column created for an entity to serve solely as the primary key and that is visible to users
  63. consists of a column that uniquely identifies an entity
    -Also called a logical key or an intelligent key
  64. Security
  65. You must be able to check the output of a CASE tool
  66. Functional Dependency
  67. no primary key attribute can be null.
  68. SELECT TripName
    FROM Trip
    WHERE Type='Hiking' AND Distance >6;
  69. Second
  70. entities
  71. Weak
  72. True
  73. Relationships
  74. primary key
  75. A functionally determines B
  76. relationship
  77. Insertion
    Deletion
    Modification
  78. SELECT TripName, State
    FROM Trip
    WHERE Season='Summer'
    ORDER BY State, TripName;
  79. entity integrity rule
  80. Physical
  81. true
  82. column(s) that could have been chosen as a primary key but was not
  83. Third
  84. a. each nonkey attribute is functionally dependent upon it.
    b. the key must be nonredundant.
    c. the key must uniquely identify the row.
    (All of the above)
  85. column(s) in one table that is required to match value of the primary key for some row in another table or is required to be null
  86. primary key
  87. False
  88. rectangles
  89. columns of interest strictly for retrieval purposes
  90. SELECT COUNT (*)
    FROM Trip
    WHERE Type='Hiking' OR Type='Biking'
  91. lines
  92. False
  93. CREATE TABLE
  94. Third
  95. CHAR
  96. Integrity constaints
  97. False
  98. DROP INDEX
  99. Foreign Key
  100. the subquery query
  101. Referential integrity contraint
  102. Aggregate
  103. True
  104. DBMSs (Data Base Management Systems)
  105. Partial functional
  106. SELECT-FROM-WHERE
  107. referential integrity constraint.
  108. create a new table whose primary key is the combination of the primary keys of the original tables
  109. False
  110. candidate key
  111. True
  112. attributes
  113. Enterprise Key
  114. no primary key attribute can be null
  115. True
  116. completed independently of any particular DBMS
  117. First
  118. information-level design adapted for the specific DBMS that will be used
    Must consider characteristics of the particular DBMS
  119. one-to-many
  120. One-To-Many
  121. Forms
  122. First
  123. exists to implement a many-to-many relationship