...

Totalnum Scripts (patient counting scripts) have been updated to improve the 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. Support for multiple fact tables has been added and bugfixes have been made.

Totalnum Scripts Setup

1. If upgrading, create the totalnum and totalnum_report tables. In Release_1-7/Upgrade/Metadata, run the ant upgrade script.
   ant -f data_build.xml upgrade_tables_release_1-7-12a
2. In  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 
3. Set privileges: If using multiple schemas, the stored procedure should be run from the metadata schema. Make sure the stored procedure can read the tables in the crcdata schema (observation_fact, visit_dimension, patient_dimension) and can both read an update ontology tables in the metadata schema (including table_access). 
4. 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
   
   If running the counting script in SQL Server, add the wildcard flag, to ignore multifact references in the ontology:
         e.g. exec RunTotalnum 'observation_fact_view','dbo','@','Y'
   This is automatically accounted for in the other database platforms.
   Note this approach does not work if you have conflicting concept_cds across fact tables.

5. 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   
   • Execute the RunTotalNum  stored procedure manually against your database from a SQL Client. This can take several hours.  Examples are below. 

Running the totalnum stored procedure directly

...