Question types

Start with

Question limit

of 68 available terms

Print test

68 Multiple choice questions

  1. • The database must already meet the requirements of both 1NF and 2NF.
    • The database must not contain any columns that aren't fully dependent upon the primary key.
  2. an attribute or set of attributes that can be used to uniquely identify each row.
  3. with a non-clustered index
  4. Transact-SQL script statements
  5. • Columns containing a unique key constraint may contain only one row with a NULL value.
    • A table may have multiple unique constraints.
  6. "provide a fact about the key, the whole key, and nothing but the key."
  7. same record in the primary key table.
  8. secondary table.
  9. to a primary key (...)
  10. The data in the rows are sorted in only one order.
  11. primary key is defined for a table.
  12. SSMS »» . Right-click the table and select Design view »» Table Designer »» Select Relationships »» Select the table to which you wish to add the foreign key constraint »» Tables and Columns Specification »» Click the ellipsis (. . .) »» Select the table that your foreign key refers to in the primary key table »» OK »» Close »» Save All
  13. functionally dependent upon the entire primary key.
  14. locking contention and improves multiple-user performance.
  15. Primary keys, foreign keys, and composite (unique) keys.
  16. NULL value in the same option, as that would violate the unique constraint's duplicate value error.
  17. enforce the uniqueness property of columns, in addition to a primary key within a table.
  18. Isolate independent multiple relationships
  19. the composite primary key plays an important role.
  20. alternate keys.
  21. attribute depends on the key but also on another nonkey attribute.
  22. All the potential primary keys.
  23. B-tree
  24. uniquely identifies each row of data.
  25. • The table must have no duplicate records.
    • The table also must not have multivalued attributes..
    • The entries in the column or attribute must be of the same data type.
  26. increases the speed of data retrieval.
  27. difficult to modify.
  28. Eliminate redundant data
  29. SSMS »» right-clicking the table and selecting Design »» Table Designer »» select Indexes/Keys »» Click on the Add button to create a new key »» the Type property in the right side of the property box and change it from the default of Index to Unique Key »» Columns property section, Click (. . .) »» Close »» Save All
  30. clustered table
  31. "many-to-many" relationship between the Customer and Products tables.
  32. corresponding values in the primary key table.
  33. you define more than one column as your primary key.
  34. • Tables that define entities
    • Tables that relate entities
  35. an attribute depends on only part of the key.
  36. foreign key.
  37. unique and must have a value that is not null.
  38. the fourth normal form
  39. the design violates the fourth normal form.
  40. each attribute does in fact describe the entity.
  41. transitive dependency
  42. logical or software-based.
  43. foreign key in one of the tables to the primary key of the referenced table.
  44. the elimination of redundant data to save space.
  45. We can simply compute the TOTAL "on the fly" when performing database queries.

    We can now use the following query in order to achieve the same results, without violating normalization rules:

    SELECT OrderNumber, UnitPrice * Quantity
    AS Total
    FROM WidgetOrders
  46. SSMS »» Databases folder »» Tables folder »» Indexes subfolder »» New index »» New Index properties box »» This is where you would select whether the index you are creating is to be clustered or non-clustered.
  47. Eliminate repeating groups
  48. primary key; without a primary key, it's not a valid table.
  49. not fully dependent on the primary key.
  50. mechanisms that are used to prevent simultaneous changes to the database
  51. • Development costs
    • Usability
    • Extensibility
  52. attribute1 is dependent on attribute2, which is then dependent on the primary key.
  53. the process of organizing data in order to reduce redundancy by dividing a database into two or more tables and then defining table relationships.
  54. transitive dependencies.
  55. two
  56. you have met the first normalized form criterion.
  57. moving the nondependent attribute to a new entity.
  58. Isolate semantically related multiple relationships
  59. Eliminate columns not dependent on key
  60. overwritten by another transaction that executes at the same time.
  61. development costs.
  62. heap.
  63. one
  64. second normal form.
  65. understand a database and write correct queries.
  66. physical
  67. SQL Server Management Studio.
  68. resolve the repeating group of tour attributes into a single unique attribute and then move any multiple values to a unique table.