1 / 31

Automating ArcSDE Geodatabase Maintenance

Automating ArcSDE Geodatabase Maintenance. 2011 IGIC Conference Muncie, Indiana Presenter: Trent Pell, GISP. History. MCCOG is a Metropolitan Planning Organization(MPO) MCCOG provides GIS and Planning support to Madison County Approximately 130,000 in population

jenis
Download Presentation

Automating ArcSDE Geodatabase Maintenance

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Automating ArcSDEGeodatabaseMaintenance 2011 IGIC Conference Muncie, Indiana Presenter: Trent Pell, GISP

  2. History • MCCOG is a Metropolitan Planning Organization(MPO) • MCCOG provides GIS and Planning support to Madison County • Approximately 130,000 in population • Approximately 86,000 land parcels • Approximately 450 sqaure miles • County/Community in transition • Largest City: Anderson

  3. GIS Overview • Automation on a single SDE Geodatabase • Versioned w/global ID’s • Multiple Editors • RDMS is SQL Server 2008 R2 (processor license) • Windows 7 & Server 2008 R2 – 64 bit • ArcGIS Server 10sp1 Standard Enterprise Edition

  4. Why Automate? • Performance • Streamlines process • After hours • Why not!

  5. What Should be Automated? • Rebuild Database Statistics • Compress Database • Reconcile & Post database versions • Delete & Re-create Versions • Sync Database changes to Web Geodatabase

  6. Process • Rebuild Statistics • Compress Database • Reconcile & Post versions to Default • Kill all connections to Database • Stop Web Services • Delete all versions • Compress Database • Rebuild Statistics • Re-create Versions

  7. Rebuild Statistics • Analyze Tool • Updates database statistics of business tables, feature tables, and delta(adds & deletes) tables • Create model & export as python script • Run on client machine

  8. Statistics

  9. Compress Database • SDE command line • Sdeversion –o compress –u sde –p password –i ServiceName -N • Batch file on server

  10. Compress Database Uncompressed State Tree Compressed State Tree

  11. Reconcile & Post Versions to Default • Reconcile Tool • Create model & export as python script • Run on client machine

  12. Reconcile & Post Version to Default

  13. Kill Connections to Database • SDE command line • sdemon -o kill -t all -p password -N -i Madison_Managed • Batch file on server • Stop WebServices accessing database • AGSSOM arcscript command • Batch file on server • cd C:\Users\tpell\Desktop\AGSSOMv10.0 AGSSOM.exe -x WebServiceName

  14. Delete Versions • SDE command line • Sdeversion –o delete –V VersionName –N –u VersionOwnerName –p VersionOwnerPassword –i ServiceName • Batch file on server • Delete your QA version LAST!

  15. Delete Versions

  16. Cleanup! • Compress database again • Re-run Analyze/Re-build Statistics • Re-Create Versions • SDE command line • Batch file on server

  17. Final Compress

  18. Re-Create Versions

  19. Automation • Utilize Windows Task Scheduler on both client and server • Allow ample time for each task to complete

  20. Automation Time-Line • 1am - Rebuild Statistics • 1:30am - Compress Database • 1:45am - Reconcile & Post versions to Default • 2am - Kill all connections to Database • 2:15am - Stop Webservices • 2:30am - Delete all versions • 2:45am - Compress Database • 3am - Rebuild Statistics • 3:30am - Re-create Versions

  21. Automation – Windows Task Schedule

  22. Automation – Triggers

  23. Automation – Actions • Browse to necessary program or file • For python scripts browse to the python.exe • Python scripts require arguments • Argument is just the python file • For batch files just browse to the .bat file

  24. One Step Further • Automate changes to Web based applications

  25. Getting changes to the Web • Each dataset needs to be versioned with Global IDs • One way synchronization between internal Geodatabase and ‘Web’ Geodatabase

  26. To the Web! • Stop all web services – AGSSOM batch file on server • Export, Compare & Import Schema Changes between Managed & Web Geodatabase – python script • Sync changes between Geodatabases – python script • Start Webservices – AGSSOM batch file on server

  27. Schema Changes & Replication

  28. Automation Time-Line • 1am - Rebuild Statistics • 1:30am - Compress Database • 1:45am - Reconcile & Post versions to Default • 2am - Kill all connections to Database • 2:15am - Stop Webservices • 2:30am - Delete all versions • 2:45am - Compress Database • 3am - Rebuild Statistics • 3:30am - Re-create Versions • 3:45am - Export Replica Schema • 4:15am - Compare & Import Replica Schema • 4:45am - Sync Managed & Web Geodatabases • 5:15am – Start Webservices

  29. Useful Tools • PythonWin • ArcScript AGSSOM tool • Geodatabase Toolset or GDBT • SDE command line is your friend

  30. Lessons Learned • Communicate • TEST! • Make Backups • Local security settings • Ensure user on server has Log as a Batch Job privleges under Local Security Policy>User Rights Assignment • Be flexible with your time-line and implementation

  31. Thank You! Trent Pell, GISP GIS Coordinator Madison County Council of Governments tpell@mccog.net 765-641-9695

More Related