transaction management

DM-40 - Managing versioned geospatial databases
  • Describe an application in which it is crucial to maintain previous versions of the database
  • Describe existing algorithms designed for performing dynamic queries
  • Demonstrate how both the time criticality and the data security might determine whether one performs change detection on-line or off-line in a given scenario
  • Explain why the lack of a data librarian to manage data can have disastrous consequences on the resulting dataset
  • Produce viable queries for change scenarios using GIS or database management tools
DM-39 - Reconciling database change
  • Design a test of reliability of change information (e.g., the logical consistency of updates to the TIGER database)
  • Implement a test of reliability of change information
DM-38 - Modeling database change
  • Describe techniques for managing long transactions in a multi-user environment
  • Describe techniques for handling version control in spatial databases
  • Define a set of rules for modeling changes in spatial databases
  • Explain why logging and rollback techniques are adequate for managing “short transactions”
DM-37 - Database change
  • Demonstrate the importance of a clean, relatively error-free database (together with an appropriate geodetic framework) with the use of GIS software
  • Exemplify scenarios in which one would need to perform a number of periodic changes in a real GIS database
  • Explain how one would establish the criteria for monitoring the periodic changes in a real GIS database
  • Discuss the implication of “long transactions” on database integrity
  • Modify spatial and attribute data while ensuring consistency within the database
DM-40 - Managing versioned geospatial databases
  • Describe an application in which it is crucial to maintain previous versions of the database
  • Describe existing algorithms designed for performing dynamic queries
  • Demonstrate how both the time criticality and the data security might determine whether one performs change detection on-line or off-line in a given scenario
  • Explain why the lack of a data librarian to manage data can have disastrous consequences on the resulting dataset
  • Produce viable queries for change scenarios using GIS or database management tools
DM-39 - Reconciling database change
  • Design a test of reliability of change information (e.g., the logical consistency of updates to the TIGER database)
  • Implement a test of reliability of change information
DM-38 - Modeling database change
  • Describe techniques for managing long transactions in a multi-user environment
  • Describe techniques for handling version control in spatial databases
  • Define a set of rules for modeling changes in spatial databases
  • Explain why logging and rollback techniques are adequate for managing “short transactions”
DM-37 - Database change
  • Demonstrate the importance of a clean, relatively error-free database (together with an appropriate geodetic framework) with the use of GIS software
  • Exemplify scenarios in which one would need to perform a number of periodic changes in a real GIS database
  • Explain how one would establish the criteria for monitoring the periodic changes in a real GIS database
  • Discuss the implication of “long transactions” on database integrity
  • Modify spatial and attribute data while ensuring consistency within the database
DM-40 - Managing versioned geospatial databases
  • Describe an application in which it is crucial to maintain previous versions of the database
  • Describe existing algorithms designed for performing dynamic queries
  • Demonstrate how both the time criticality and the data security might determine whether one performs change detection on-line or off-line in a given scenario
  • Explain why the lack of a data librarian to manage data can have disastrous consequences on the resulting dataset
  • Produce viable queries for change scenarios using GIS or database management tools
DM-39 - Reconciling database change
  • Design a test of reliability of change information (e.g., the logical consistency of updates to the TIGER database)
  • Implement a test of reliability of change information

Pages