MétaCan
Menu
Back to cohort
Record W2154223184 · doi:10.1109/itng.2011.100

Employing Frequent Pattern Mining for Finding Correlations between Tables in Relational Databases

2011· article· en· W2154223184 on OpenAlexaff
Ali Rahmani, Mohamad Nagi, Mohammad Rifaie, Keivan Kianmehr, Mick Ridley, Reda Alhajj, Jon Rokne

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Database Systems and Queries
Canadian institutionsWestern UniversityRoyal Bank of CanadaUniversity of Calgary
Fundersnot available
KeywordsComputer scienceRelational databaseData miningDatabaseDatabase designDatabase schemaRelational modelDatabase modelViewTable (database)RowSet (abstract data type)Information retrieval

Abstract

fetched live from OpenAlex

Knowledge of the dependencies and correlations which exist between data units in a relational database is of paramount importance when designing a distributed database since discovering such correlations would be crucial for reaching an optimal data distribution. The knowledge may also be used to improve the performance of a centralized database through a reorganization process. In this paper, we propose a data mining approach for identifying groups of correlated tables in a relational database schema by considering the work profile of the database. We analyze the query history to find sets of tables that are frequently accessed together. The sets of tables that are found overlap in general and we therefore turn each set of tables into a fuzzy set and determine the degree of membership of each table in each of the fuzzy sets. Our approach offers a high degree of flexibility and can be easily customized to produce result with desired amount of detail. The outcome will be highly valuable for guiding a database administrator in producing a better allocation plan. It also guides the database designer in deriving a well optimized fragmentation plan. Our experiment shows the viability and power of our approach. The proposed approach can also be extended to find correlations between smaller data units such as fragments, rows or columns.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.387
Threshold uncertainty score0.398

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.196
GPT teacher head0.315
Teacher spread0.120 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2011
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Database Systems and QueriesFrench-language works237,207