Changes to make Centralized data smaller: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
mNo edit summary
Line 10: Line 10:
  | todo_action = 2022-08-10
  | todo_action = 2022-08-10
  | question =   
  | question =   
* update CFE to stop pulling these tables from Centralized (need to find out if CFE really still needs these at all)
* update CFE re-link to these in Legacy rather than in Centalized_Data
}}
}}


Revision as of 15:20, 2022 August 10

As of 2022-08-10 Centralized data.mdb was 1.348GB . This is large and slowly approaching MS Access' 2GB limit. The size also makes it slow to copy down, and even slower to copy up. This page is about attempts to make the file smaller.

L_Dxs table and L_Como table

We can reduce the file size to 0.810GB by moving the legacy tables L_Dxs table and L_Como table to Legacy TMS Data.mdb. These tables are “stale” and no longer change, so we don’t really need to have them in Centralized data.mdb.

Next Steps
  • update CFE re-link to these in Legacy rather than in Centalized_Data
  • added: 2022-08-10
  • action: 2022-08-10
  • Cargo


  • Categories

Log

    • asked Julie to change her SAS to pull them from there and update here when done
  • SMW


  • Cargo


  • Categories

Postal_Code_Master table

Further, we have a Postal_Code_Master table in there. It’s in Centralized Data only because Pagasa maintains it, so if it was in CFE it would get lost if I make an update to that file. But there is no reason it couldn’t live in a different file, that would just have to be added to the push pull machinery for Pagasa. Removing this table further shrinks the file to 0.721GB

Next Steps
  • Tina to figure out
  • added: 2022-08-10
  • action: 2022-08-10
  • Cargo


  • Categories

Log

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Changes_to_make_Centralized_data_smaller&oldid=157108"