Dr. Peeter Kirs

__ Aborted transactions

__ Accidental data losses

__ Authorization Rules

__ Backup Facilities

__ Backward Recovery

__ Checkpoint Facilities

__ Cold Backup

__ Conceptual Statistical Database Model

__ Concurrency Control

__ DA/DBA Shared Reponsibilities

__ Data Administration Functions

__ Data Administrator

__ Data Analysis

__ Data Conlict Resolution

__ Data Dictionary

__ Data Integrity

__ Data Integrity Controls

__ Data Perturbation

__ Data Planning

__ Data Policies

__ Data Procedures

__ Data Repository

__ Data Security

__ Data Standards

__ Database Administrator

__ Database Atomicity

__ Database Backup

__ Database Change Log

__ Database Design

__ Database destruction

__ Database Durability

__ Database Implementation

__ Database Isolation

__ Database Locking

__ Database locks

__ Database Operations and Maintenance

__ Database Performance Tuning

__ Database recovery

__ Database Security

__ Database Security Management

__ Database Serializability

__ Database Steward

__ Database Switch

__ Database Views

__ Deadlock

__ Deadlock detection/resolution

__ Deadlock Prevention

__ Default Values

__ Domain Restrictions

__ Encryption

__ Exclusive Locks

__ Field locks

__ Forward Recovery

__ Growth and Change Management

__ Hot Back-up

__ Improper data access

__ Inconsistent retrievals

__ Incorrect data

__ Information Repository

__ Internal Marketing

__ I/O Contention

__ Journalizing Facilities

__ Lock Granularity

__ Loss of Availabilty

__ Lost Updates

__ Output Perturbation
__ Query Restiction

__ Page Locks

__ Probability Checks

__ Recovery Manager

__ Run/Restore
__ Self-Checking Procedures

__ Shared Locks

__ Software Selection

__ Statistical Databases

__ System Failure

__ Systems Catalog
__ Table Locks
__ Threats to security

__ Time Stamping

__ Transaction

__ Transaction Log

__ Transaction Scheduling

__ User authentication schemes
__ Versioning

__ Warehouse Administration

01. Implies that a transaction is a single (indivisible), invisible, logical unit of work

02. Includes the enforcement of standards and training

03. Management of simultaneous transactions In a multi-user environment

04. Includes, for example, the use of check-digits

05. A high level position responsible for data resource management

06. Documents the data and metadata elements of a database

07. A Selected portion of database is shut down during back-up

08. Implies that when accessed, all records necessary are X-Locked

09. Includes thefts and fraud and improper data access

10. May be caused by sabotage or viruses

11. Databases which allow access to general information without revealing individual data elements

12. Includes such measures as firewalls and establishment of user priviledges

13. Mechanisms for restoring a database quickly and accurately after loss of damage

14. Each concurrent transaction is treated as thought they were received and executed one after another

15. A pre-specified amount of data (that which is read into memory)  is made unavailable to the user

16. Implies that a transaction must be permanent

17. Occur when a transaction calculates results while another operation is taking place

18. Rules which restrict access

19. 2 mirror-image databases maintained

20. An Impasse resulting from two or more transactions locking the same data at the same time

21. Queries results are altered before they are presented to the user

22. The world’s second oldest profession

23. The entire database is made unavailable to the user

24. Interactions which are terminated due to human error, input of invalid data, loss of transmission, or other reasons

25. When the DBMS temporarily halts all activities and synchronizes all files and journals

26. Only the record requested is made unavailable

27. A Data Administration function intended to “sell” the system to management

28. Multiple users can read, but not update, the data

29. The statement of goals, objectives and targets

30. Unwanted changes are undone through the use of Before images (in the Database Change Log)

31. Includes logical and Physical design

32. A DBMS component that restores the database to a correct condition and restarts processing activities

33. Failure to include a database transaction

34. Used to maintain audit trails of transactions and logs of database changes

35. Involves both the DA and DBA

36. Only the datasets with common attributes and their statistics are made available

37. Data which is valid but not correct

38. A systems-generated catalog that describes the database objects

39. A technical function that is responsible for database design

40. Includes the use of statistical databases and authorization rules

41. Includes Power loss, operator error, systems software failure

42. A logical unit of work that must be either entirely completed or aborted

43. Contains the metadata that describes an organization’s data

44. Includes Database Planning and Conflict Resolution

45. Contains before and after images of database transactions

46. The entire table is made unavailable to the user

47. Interleaves (meshes) the execution of database operations to ensure serializability

48. Intended to answer the question “Who owns the data?”

49. The entire database is altered so that the characteristics remain the same but individual elements are non-sensical

50. Data provided by a transaction can not be used by a later transaction until the first transaction is complete

51. Attempts to verify that users are who they claim to be

52. A Record of essential data for each transaction processed against the database

53. Data can not be accessed, even for reading, by other users

54. The DBMS periodically scans for deadlocks and resolves deadlocks

55. Involves providing protection against accidental or intentional loss of data

56. Periodic back-up copies of the entire database

57. Each time a record is requested, the DBMS creates a copy of the information requested

58. Includes the use of Default Values, domain restrictions, and checking routines

59. A relatively new function due to the emphasis on gathering massive amounts of data from multple sources

60. Includes user training and developmen of access policies

61. The unique, monotonic time applied to each transaction

62. The present emphasis is on “off-the-shelf” packages

63. Can result in a loss of privacy or confidentiality

64. A statement of actions to be applied for a specific activity

65. Previous transactions are reprocessed against the backup copy of the database

66. Deciding who gets what and when

67. Includes the maintenance of data relationships

68. Involves the clustering individual entities in mutually exclusive subsets

69. Includes monitoring of CPU loads and modification of SQL Code as necessary

70. After images (in the Database Change Log) are applied to the Database Backup

71. Includes Human error and hardware/Software failure

72. The checking of the likelihood of an event occuring

73. The level at which data is locked to the user

74. Includes data about the data processing resources

75. Requires that only certain values can be entered

76. Includes Database Implementation and User training

77. An Administrative function that is responsible for assuring that applications meet organizational goals

78. The database is lost, destroyed, or can not be read

79. A statement of conventions to be followed in data usage

80. Implies that the entire database is shut-down while back-up occurs

81. The denial of access to another transaction until the previous transaction is committed

82. The insertion of values that are entered when no entry is made

83. An SQL creation which enables users to access data without having to know the physical structure of the database

84. Involves the duplication of a database in case the system “crashes”

85. Includes development of the enterprise model

86. Includes definition of business rules