1 / 13

Data Caching Strategies for Checking Integrity Constraints of Mobile Database

This article explores data caching strategies for checking integrity constraints in mobile databases without a permanent connection. It discusses methods for determining if database rules have been violated and presents caching strategies to improve speed and minimize data downloads.

sburton
Download Presentation

Data Caching Strategies for Checking Integrity Constraints of Mobile Database

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Zarina Dzolkhifli, Hamidah Ibrahi, Lilly Suriani Affendey Presented by: Phillip Cunningham Data Caching Strategies for Checking Integrity Constraints of Mobile Database

  2. Title • Data Caching Strategies • Store only relevant and necessary information. • Checking Integrity Constraints • How will we determine if the rules of our database have not been violated by an update?

  3. Title (cont.) • Mobile Database • Any mobile application of a database which stores the data locally. • In particular for this article the concern is with mobile databases without a permanent connection to a centralized database.

  4. What is the point?(In English) • To verify that our database will be happy with the changes made to it on a mobile device when it is not connected to a data network, and how we can do that most effectively. • Put simply, we want to make sure that we won't break our database.

  5. Is there anything that already does this? • Yes, to a degree. • There is a system which verifies with a base system over a network that the database is still okay. • The mobile host is required to connect to at least one 'node' of the distributed database system that is wired and kept up-to-date with all data.

  6. Is there anything that already does this? • The goal of obtaining a mobile system that does not need to connect to a node to verify the consistency of the database after the update is unique. • Checking constraints efficiently has been done in centralized systems, but not for a mobile device that can do it on its own.

  7. Method • 1.) Given an update operation, U, determine which integrity tests might be violated • 2.) Group the tests based on criteria such as: • Relation specified in tests • Grouped by type of test (complete/sufficient) • Where they must be evaluated (local or not) Each group has at least one test from each integrity constraint.

  8. Method (cont.) 3.) Derive internal representation of integrity tests.

  9. Rule 1: If two tests require the same set of data they are redundant Rule 2: If one test requires a subset of the data of another test it is subsumptive. Method (cont.) 4.) Analyze relationships between the tests. • Redundant • Subsumptive

  10. Experiments This compares different caching methods for a specific database and two transactions. Strict Strategy and Relaxed Strategy are those put forth by the authors.

  11. More Experiments When adding more tuples to the tables involved RS and SS still cached the same amount of tuples.

  12. Considerations • These are good strategies to improve speed and keep the mobile device from needing to download the entire database. • This won't actually allow for verifying transactions if you don't have the right data already on your phone and are disconnected.

  13. Questions ?

More Related