Changes to make Centralized data smaller: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
JMojica (talk | contribs)
CCMDB_legit, admin, approved, Administrators
2,545 edits
No edit summary
mNo edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
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.  
As of 2022-08-10 [[Centralized data.mdb]] was 1.348GB . This is large and slowly approaching MS Access' 2GB limit. The size also made it slow to copy down, and even slower to copy up. We made some changes to reduce the size by [[#Removing the L_Dxs table and L_Como table]] and [[#Reducing fields and field sizes in the Postal_Code_Master table]]. This initiative is now complete.  


=== [[L_Dxs table]] and [[L_Como table]] ===
=== Removing the [[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]].  
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 ====
{{Todo
| who = Tina
| todo_added = 2022-08-10
| todo_action = 2022-08-10
| question = 
* after Pagasa has legacy local, remove tables from Centralized master.
}}


==== Log ====
==== Log ====
* 2022-08-31: Teams with Pagasa where we removed the [[L_Dxs table]] and [[L_Como table]] from [[Centralized data.mdb]]
* 2022-08-10:  
* 2022-08-10:  
** emailed Pagasa to copy Legacy to local
** emailed Pagasa to copy Legacy to local
Line 21: Line 13:
** Julie copied the  [[Legacy_TMS_Data.mdb]] to local where SAS will pull from (08Aug2022 )
** Julie copied the  [[Legacy_TMS_Data.mdb]] to local where SAS will pull from (08Aug2022 )


 
=== Reducing fields and field sizes in the [[Postal_Code_Master table]] ===
=== [[Postal_Code_Master table]] ===
There is a [[Postal_Code_Master table]] in [[Centralized data.mdb]]. The table is likely in the correct Access file because Pagasa maintains it and Julie uses it.  
There is a [[Postal_Code_Master table]] in [[Centralized data.mdb]]. It’s in this file because Pagasa maintains it, so if it was in [[CFE]] it would get lost if Tina made an update to that file. Removing this table would further shrink the file to 0.721GB .
 
{{DJ |
* Do you actually use this table? If so we might need to keep it in Centralized so you get any updates Pagasa makes. [[User:Ttenbergen|Ttenbergen]] 16:38, 2022 August 10 (CDT)
* The table has a lot of fields that are only populated for MB, an not even consistenly there. Do you use any of these fields for aggregation? Do you use this table at all when you do geographic analysis, or do you have a different one? They are all 255char fields, so if there are any we don't use we should consider eliminating them. There are also some erratic entries in there, eg. latitudes and longitudes missing their decimal points, or rhacode and province blank... do we need to review this? [[User:Ttenbergen|Ttenbergen]] 16:38, 2022 August 10 (CDT)
** yes I use the table  and particularly helpful for MB where the RHA are listed.  i do not use the latitudes or longitudes.  if occupying more space, one option is to separate the MB from the rest.  maybe save the rest to another accdb but  keep the MB.  besides, new postal codes often occur at WPG/MB.  ---[[User:JMojica|JMojica]] 09:44, 2022 August 11 (CDT) }}
 
If Pagasa is the only user of this table we could move it into a different file, which would just have to be added to the push pull and reconnect machinery for Pagasa.  
 
==== Next Steps ====
{{Todo
| who = Tina
| todo_added = 2022-08-10
| todo_action = 2022-08-10
| question =  _after
* Waiting for info from Julie:
** Can we move the file out? [[User:Ttenbergen|Ttenbergen]] 16:38, 2022 August 10 (CDT)
** Can we reduce field sizes? [[User:Ttenbergen|Ttenbergen]] 16:38, 2022 August 10 (CDT)
}}


==== Log ====
==== Log ====
* removed "code" fields that duplicate "name" field data, and reduced field sizes as much as possible, which reduced table size from ~89MB to ~70MB.


== Related articles ==  
== Related articles ==  

Latest revision as of 14:19, 2022 September 1

As of 2022-08-10 Centralized data.mdb was 1.348GB . This is large and slowly approaching MS Access' 2GB limit. The size also made it slow to copy down, and even slower to copy up. We made some changes to reduce the size by #Removing the L_Dxs table and L_Como table and #Reducing fields and field sizes in the Postal_Code_Master table. This initiative is now complete.

Removing the 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.

Log

Reducing fields and field sizes in the Postal_Code_Master table

There is a Postal_Code_Master table in Centralized data.mdb. The table is likely in the correct Access file because Pagasa maintains it and Julie uses it.

Log

  • removed "code" fields that duplicate "name" field data, and reduced field sizes as much as possible, which reduced table size from ~89MB to ~70MB.

Related articles

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