Page History
...
Totalnum Scripts have been updated to improve the Totalnum counter performance on both many ontology tables and very large(>1.5 million) ontologies such as ACT medications. Debug messages have also been added for troubleshooting and profiling purposes
Totalnum Scripts Setup
- In the Release_1-7/NewInstall/Metadata/ run the ant script to create the stored procedures.
ant -f data_build.xml create_metadata_procedures_release_1-7 - Run the stored procedures on your database. This can be done in two ways:
- Run the ant command to execute the data_build.xml file with below specified target
POSTGRESQL : ant -f data_build.xml db_metadata_run_total_count_postgresql
ORACLE : ant -f data_build.xml db_metadata_run_total_count_oracle
SQL SERVER : ant -f data_build.xml db_metadata_run_total_count_sqlserver - If using multiple fact tables, the recommended approach is to 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 with the wildcard flag, to ignore multifact references in the ontology e.g., in SQL Server, exec RunTotalnum 'observation_fact_view','dbo','@','Y' Note this approach does not work if you have conflicting concept_cds across fact tables.
- Execute the RunTotalNum stored procedure manually against your database in from a sql Client. This can take several hours. Example Usage:
- Run the ant command to execute the data_build.xml file with below specified target
...
Application Type | Java | Wildfly | Apache HTD | Apache Ant | Apache Axis2 | PHP |
---|---|---|---|---|---|---|
Supported Version/s | 8 or 11 | 17.0.0 | 2.4.17 or higher | 1.9.6 | 1.7.1 | 7.2.27 or higher |
i2b2 Database Changes
New db updates |
---|
|
|
|
|
|
|
i2b2 Server and Client Changes
...