chapter 13 Flashcards
What is a distributed DBMS?
data is distributed across multiple systems
distribution by design
4 layer schema architecture: external schema, global conceptual schema, local conceptual schema, local internal schema
Distribution strategies: horizontal partitioning, vertical partitioning, partial replication (to improve performance).
tightly coupled. Heterogenity is not an issue.
What is a federated DBMS?
Its a DBMS based on a global, federated conceptual schema. It describes integrated view of all participating data sources using the canonical data model. It realizes distribution transparency and application can access multiple data sources withing the same query.
What are the alternatives for federated schema creation?
Bottom-up: schema integration
top-dowm: schema design, schema mapping
What is the schema reference architecture of a federated schema?
External schema, federated schema, export schema, component schema, local schema
Explain federated schema:
Includes (possibly just renames) export schema elements. May provide integrated schema (resolve structural, schematic and semantic heterogeneity).
Explain export schema:
Describes subset of local data/schema to be made available for global application
May be under the control of the local system
Explains: components schema:
describes the local DB usign global data model. Overcome data model heterogeneity
Explains local schema:
Corresponds to the conceptual schema of the local DB.
It is based on local data model
Mediator-based information systems
It’s a generalization of federated DBMS based on wrappers (for accessing data sources) and mediators (to access one or more wrappers and provide useful services)
Components mediator-based IS:
external schema; global (mediator) schema;wrapper schema; local schema
What are the tasks of the wrapper?
Encapsulate data source and provide uniform access to data. It provides infrastructure for overcoming heterogeneity among data sources: wrapper achitecture and wrapper interfaces
It helps to overcome hterogeneity of data sources regarding: data model, data acces api, query language and capabilities.
It gives support to global query evaluation and optimization.
Finally, it can be a useful infrastructure for Federated DBMS
Garlic
„Wrapper Architecture“
Wrapper architecture:
Garlic and wrapper cooperate for query processing (wrapper says its processing capabilities and garlic query engine compensates for lack of wrapper query functionality)
Garlic - How do you model data as object collections?
The wrappers supplies description of data source in garlic data language when it registries itself in garlic.
Then a garlic object exists, with an interface, at least one implementation , identity and root objects (collections)
Garlic - methods. How to call?
The methods can be called by garlic engine or by the application based on an object reference.