Databases Reference
In-Depth Information
Figure 17.1 shows how Analysis Services uses those objects to populate a partition with
data. Analysis Services locates a partition
Binding
object associated with the partition to
find out which relational table contains the data, and then it iterates over every measure
and granularity attribute in the measure group to find information about which relational
columns it needs.
TableA
Data Source View
TableB
Relational
Database
Binding
TableA
Partition
TableB
Binding
TableA
Relational
Database
FIGURE 17.1
Binding between multidimensional objects and source of data.
Typically, a binding does not reference relational tables directly. Analysis Services provides
a layer of abstraction between the multidimensional object and the relational database—
the
Data Source View
(DSV).
The bindings for the partition reference a table object in the DSV, which in turn maps to a
table, view, or query in Microsoft SQL Server (or other supported relational engine). After
Analysis Services determines what data it needs for the processing operation, it builds an
abstract query that lists all the tables and columns of the relational database.
Analysis Services builds the abstract internal query by using an abstract internal Extensible
Markup Language (XML) definition. It then translates the query to one with semantics
specific to the data source. (For example, a query for SQL Server needs different quote iden-
tifiers than a query intended for an Oracle database.) Figure 17.2 diagrams this process.
Search WWH ::
Custom Search