Along with the legacy API is the concept of major and minor objects that provide granular descriptions of object state as discovered from the server, or when saved to the server. When you manage objects not specified in tabular metadata (such as a Server or Database), you need to leverage parts of the existing AMO stack that describe those objects. TOM is built on top of the AMO infrastructure, which also accommodates multidimensional and tabular databases at compatibility levels below 1200. The lowest level descendant of any parent object in this hierarchy is an Annotation object that can be used to optionally extend the schema as long as you provide the code to handle it. For example, the Model object contains a collection of Table objects (via the Tables property), with each Table object containing a collection of Column objects, and so on. With the exception of AttributeHierarchy, KPI, and LinguisticMetadata, each child object can be a member of a collection. Server and Database are not considered tabular because these objects can also represent a multidimensional database hosted on a server running in Multidimensional mode, or a tabular model at a lower compatibility level that does not use tabular metadata for object definitions. Tabular object model hierarchyįrom a logical perspective, all tabular objects form a tree, the root of which is a Model, descended from Database. To review the full list of programming options for tabular models, including script and query language support, see Tabular Model Programming for Compatibility Level 1200. To learn more about specific AMO/TOM classes, see Microsoft.AnalysisServices Namespace reference. See Install, distribute, and reference the Tabular Object Model () for details. Your code will need to reference both assemblies. General-purpose classes of AMO were moved to assembly. A high-level view of the object model tree, provided below, illustrates how the component parts are related.īecause TOM is an extension of AMO, all classes representing new tabular objects are implemented in a new assembly. TOM exposes native tabular metadata, such as model, tables, columns, and relationships objects. As with AMO, TOM provides a programmatic way to handle administrative functions like creating models, importing and refreshing data, and assigning roles and permissions. For example, a query could be set up to determine all the groundwater measurements taken from monitoring well #5 in 1996.The Tabular Object Model (TOM) is an extension of the Analysis Management Object (AMO) client library, created to support programming scenarios for tabular models created at compatibility level 1200 and higher. When tables are relationally linked, queries can be set up to pull specified information from multiple tables. In this example, the location table is linked to the groundwater levels table through the common LOC_ID field. Tables are related in the database through key fields. Some of the information it contains includes location identifiers, location coordinates, and location type, such as monitoring well or soil boring. Here you see the design view of the Location table from the database. The tables are essentially spreadsheets with columns of data. Each table contains specific information related to the database subject, which in this project is environmental conditions at the facility. If you are unfamiliar with databases, the data is stored in tables. Besides the spatial database, we also have an extensive relational tabular database that we have created using Microsoft Access.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |