chapter 13 Flashcards

1
Q

What is a distributed DBMS?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is a federated DBMS?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the alternatives for federated schema creation?

A

Bottom-up: schema integration

top-dowm: schema design, schema mapping

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the schema reference architecture of a federated schema?

A

External schema, federated schema, export schema, component schema, local schema

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Explain federated schema:

A

Includes (possibly just renames) export schema elements. May provide integrated schema (resolve structural, schematic and semantic heterogeneity).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Explain export schema:

A

Describes subset of local data/schema to be made available for global application
May be under the control of the local system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Explains: components schema:

A

describes the local DB usign global data model. Overcome data model heterogeneity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Explains local schema:

A

Corresponds to the conceptual schema of the local DB.

It is based on local data model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Mediator-based information systems

A

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)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Components mediator-based IS:

A

external schema; global (mediator) schema;wrapper schema; local schema

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the tasks of the wrapper?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Garlic

A

„Wrapper Architecture“

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Wrapper architecture:

A

Garlic and wrapper cooperate for query processing (wrapper says its processing capabilities and garlic query engine compensates for lack of wrapper query functionality)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Garlic - How do you model data as object collections?

A

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)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Garlic - methods. How to call?

A

The methods can be called by garlic engine or by the application based on an object reference.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Garlic - what are the mechanisms to invoke an method?

A
stub dispatch (natural if data source provides object class libraries)
Generic dispatch (wrapper provides one entry point and it is schema independent)
17
Q

Garlic - query planning. How it works?

A

Garlic optimizer builds the query plan using a bottom-up approach. the wrappers participate in query planning process.

18
Q

What are the methods the wrapper provides to be used by Garlic work requests?

A

Plan_access()
Plan_join()
Plan_bind()

19
Q

What is the result of a work request?

A

Sets of plans
Each plan contains a list of properties that describe which parts of the work request are implemented by the plan and what the costs are.

20
Q

What are the components the wrapper packeging provides in a package?

A

Interface facile (GDL definitions), enviroment files, libraries

21
Q

What is a foreign data server?

A

It is a server that manages data soreted outside the SQL server. In this case SQL server and SQL client use foreign server descriptors to communicatte with foreign servers.

22
Q

What is a foreign table?

A

it’s atable sotred in a foreign server or dynamically generated by foreign wrapper capabilities

23
Q

A multi-database system

loose coupling of systems.

A

It has no global schema (the actual integration needs to be performed by the application)
It has multi-database language.

24
Q

what are the limitations of SQL?

A

STANDARD SQL is unable to generically solve most forms of schematic heterogeneity.

25
Q

Define Schematic Query Languages

A

It is a solution that extends SQL to be able to transform data to metadata (and v.v.)
In additional, schematic query languages provide mechanism to access different databases in a single query

26
Q

What are the 6 operators of FIRA/FISQL?

A

????