FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W103725540> ?p ?o ?g. }

• W103725540 endingPage "925" @default.
• W103725540 startingPage "920" @default.
• W103725540 abstract "Decision support applications require complex queries, e.g., multi way joins defining on huge warehouses usually modelled using star schemas, i.e., a fact table and a set of data dimensions (Papadomanolakis & Ailamaki, 2004). Star schemas have an important property in terms of join operations between dimensions tables and the fact table (i.e., the fact table contains foreign keys for each dimension). None join operations between dimension tables. Joins in data warehouses (called star join queries) are particularly expensive because the fact table (the largest table in the warehouse by far) participates in every join and multiple dimensions are likely to participate in each join. To speed up star join queries, many optimization structures were proposed: redundant structures (materialized views and advanced index schemes) and non redundant structures (data partitioning and parallel processing). Recently, data partitioning is known as an important aspect of physical database design (Sanjay, Narasayya & Yang, 2004; Papadomanolakis & Ailamaki, 2004). Two types of data partitioning are available (Özsu & Valduriez, 1999): vertical and horizontal partitioning. Vertical partitioning allows tables to be decomposed into disjoint sets of columns. Horizontal partitioning allows tables, materialized views and indexes to be partitioned into disjoint sets of rows that are physically stored and usually accessed separately. Contrary to redundant structures, data partitioning does not replicate data, thereby reducing storage requirement and minimizing maintenance overhead. In this paper, we concentrate only on horizontal data partitioning (HP). HP may affect positively (1) query performance, by performing partition elimination: if a query includes a partition key as a predicate in the WHERE clause, the query optimizer will automatically route the query to only relevant partitions and (2) database manageability: for instance, by allocating partitions in different machines or by splitting any access paths: tables, materialized views, indexes, etc. Most of database systems allow three methods to perform the HP using PARTITION statement: RANGE, HASH and LIST (Sanjay, Narasayya & Yang, 2004). In the range partitioning, an access path (table, view, and index) is split according to a range of values of a given set of columns. The hash mode decomposes the data according to a hash function (provided by the system) applied to the values of the partitioning columns. The list partitioning splits a table according to the listed values of a column. These methods can be combined to generate composite partitioning. Oracle currently supports range-hash and range-list composite partitioning using PARTITION - SUBPARTITION statement. The following SQL statement shows an example of fragmenting a table Student using range partitioning." @default.
• W103725540 created "2016-06-24" @default.
• W103725540 creator A5006507514 @default.
• W103725540 date "2011-05-24" @default.
• W103725540 modified "2023-09-26" @default.
• W103725540 title "A Genetic Algorithm for Selecting Horizontal Fragments" @default.
• W103725540 cites W1561058006 @default.
• W103725540 cites W1565472858 @default.
• W103725540 cites W1793365533 @default.
• W103725540 cites W1978220611 @default.
• W103725540 cites W1982525351 @default.
• W103725540 cites W2055393182 @default.
• W103725540 doi "https://doi.org/10.4018/978-1-60566-010-3.ch142" @default.
• W103725540 hasPublicationYear "2011" @default.
• W103725540 type Work @default.
• W103725540 sameAs 103725540 @default.
• W103725540 citedByCount "0" @default.
• W103725540 crossrefType "book-chapter" @default.
• W103725540 hasAuthorship W103725540A5006507514 @default.
• W103725540 hasConcept C11413529 @default.
• W103725540 hasConcept C41008148 @default.
• W103725540 hasConceptScore W103725540C11413529 @default.
• W103725540 hasConceptScore W103725540C41008148 @default.
• W103725540 hasLocation W1037255401 @default.
• W103725540 hasOpenAccess W103725540 @default.
• W103725540 hasPrimaryLocation W1037255401 @default.
• W103725540 hasRelatedWork W1495151533 @default.
• W103725540 hasRelatedWork W1533716699 @default.
• W103725540 hasRelatedWork W1847735123 @default.
• W103725540 hasRelatedWork W1996035188 @default.
• W103725540 hasRelatedWork W2002369267 @default.
• W103725540 hasRelatedWork W2005333080 @default.
• W103725540 hasRelatedWork W2036652021 @default.
• W103725540 hasRelatedWork W2071413032 @default.
• W103725540 hasRelatedWork W2094305400 @default.
• W103725540 hasRelatedWork W2148961938 @default.
• W103725540 hasRelatedWork W2154605267 @default.
• W103725540 hasRelatedWork W2168703821 @default.
• W103725540 hasRelatedWork W226234260 @default.
• W103725540 hasRelatedWork W2385004514 @default.
• W103725540 hasRelatedWork W2533970107 @default.
• W103725540 hasRelatedWork W2921351239 @default.
• W103725540 hasRelatedWork W30311160 @default.
• W103725540 hasRelatedWork W3045233174 @default.
• W103725540 hasRelatedWork W2003711267 @default.
• W103725540 hasRelatedWork W2117187017 @default.
• W103725540 isParatext "false" @default.
• W103725540 isRetracted "false" @default.
• W103725540 magId "103725540" @default.
• W103725540 workType "book-chapter" @default.