SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Census Bureau

ormand avatar
ormand
14 diapositives · 281 Views · Aug 20, 2014

This report highlights the modernization efforts undertaken in the Decennial Systems Database at the Census Bureau over the last three months. Key activities include the migration of data from DE101 to BE101, creation of efficient scripts for data loading and index optimization, and implementation of improved retrieval criteria. Testing of the UECT process shows significant performance advancements compared to the old system, including reduced data load times from 30 hours to 1.5 hours. Challenges such as database compatibility were addressed with workarounds to ensure continuous progress.

#census bureau #census bureau ppt #powerpoint #presentation
Census Bureau - slide 1
01 / 14Census Bureau
1 / 17

Télécharger la présentation

Census Bureau
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Census Bureau System IPT Decennial Systems Database Modernization Support DRIS Decennial Response Integration System Date: 07/30/2007

  2. Index • What have we done in past 3 months • dscmotd1 and DE101 compare • Moved to DE101 and then to BE101 • And many more … • Work done on DE101 • Scripts creation for load • Studying application for index creation • UECT creation from UNM • Writing script based on state retrieval • Unit testing for UECT

  3. Full load • Full test for UECT load- successful • Compare times with old machine • Performance and tuning • Partitioning tables • Comparing results for 2000 • Change in retrieval criteria • Retrieval criteria to LCO basis • Changed scripts • Partitioned tables based on LCO • Unit testing and full testing • Taking advantage based on CPUs • Running scripts in parallel

  4. Move DE101 to BE101 • Move scripts from DE101 to BE101 • Test all scripts for performance • Data modeling • Version difference • Production m/c • Work around/Solution • Reverse Engineering effort

  5. What have we done in past 3 months • dscmotd1 and DE101 compare • Moved to DE101 and then to BE101 • And many more … dscmotd1 BE101 DE101 • Got acceptable and best results on DE101 • Moved schema to DE101

  6. Work done on DE101 • Scripts created for • Data load • Indexes • analyzing table objects • Study application to create proper indexes • Fast data retrieval • Fast data update • Test data load and compare with old machine • Acceptable results • Data load in 1.5 hrs for whole country compare to 30 hrs on old machine

  7. UECT creation from UNM • Scripts based on state retrieval – 2000 • Unit testing • Full load testing • Full test for UECT load- successful • Compare times with old machine UNM table UECT process UNM table Retrieval based on state

  8. Performance & Tuning • Results not up to the mark • P & T was needed • Data size, too high • table partitioning UECT process Retrieval based on state

  9. Change in retrieval criteria • Data retrieval based on LCO and NOT on state based • Unit and full testing • Advantages of CPU bound operations • Scripts run in parallel UECT process Retrieval based on LCO

  10. Moving from DE101 to BE101 • Got new host • DE101 - Production • BE101 – Beta/test • Same configuration • Whole testing to be done

  11. Data Modeling Problems • Data repository was not compatible with Database version • Could not do data modeling using Oracle designer • Work around using third party tool. No stoppage of work Oracle db 10g Desktop Data modeling X Designer repository 6.x Versions not compatible DE101

  12. Work Around • Work around using third party tool. No stoppage of work Desktop Data modeling Third party tool Oracle db 10g Versions compatible Scripts creation/ execution DE101

  13. Reverse Engineering effort – not done Oracle db Desktop Data modeling DE101 Designer repository Versions compatible BE104

  14. THE END