Totalnum performance improvements
(CORE-389)
|
|
| Status: | In Review |
| Project: | i2b2 Core Software |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.13 |
| Type: | Sub-Task | Priority: | Major |
| Reporter: | Jeffrey Klann | Assignee: | Jeffrey Klann |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Rank: | 0|s000jc: |
| Participant/s: |
| Description |
|
Add support for multiple fact tables on the totalnum counter scripts for all database platforms.
|
| Comments |
| Comment by Jeffrey Klann [ 27/Apr/22 ] |
|
Multifact by creating a large view of all fact tables now supported in all platforms. Needs to be tested in Oracle and Postgres.
To use with multi-fact setups: Create a fact table view as the union of all your fact tables. (This is essentially going back to a single fact table, but it is only used for totalnum counting. This is needed to correctly count patients that mention multiple fact tables within a hierarchy.) e.g., create view observation_fact_view as select * from CONDITION_VIEW union all select * from drug_view And then run the totalnum counter on that fact table view. |
| Comment by Jeffrey Klann [ 11/May/22 ] |
| This needs to be tested in Oracle. |
| Comment by Reeta Metta [ 30/May/22 ] |
| needs to be tested in postgres as well |
| Comment by Reeta Metta [ 14/Jun/22 ] |
|
verified only on sql server
currently no db set up for oracle and postgres |
| Comment by Jeffrey Klann [ 14/Jun/22 ] |
| This has been tested on Oracle by Ngan Chau at UCLA. |
[CORE-398]