Software and Data Compress Full geodatabase Stand-alone feature classes Feature dataset Raster dataset Result All feature classes, feature datasets, and tables compressed A single feature class compressed All feature classes in the feature dataset compressed Compression already applied through pyramid creation Learn More Several courses on building and using geodatabases are offered by Esri. Visit www. esri.com/training to learn more about these offerings. n Building Geodatabases, an instructor-led course n Creating and Editing Geodatabase Features with ArcGIS Desktop (for ArcEditor and ArcInfo), a Web course n Introduction to the Multiuser Geodatabase, an instructor-led course n Creating, Editing, and Managing Geodatabases for ArcGIS Desktop, a Web course Effects of compression on data storage Sample data U.S. census block centroids California roads Manhattan, NY parcels Vegetation data Riverside, CA buildings Uncompressed size 705 MB 329 MB 4.42 MB 3.31 MB 644 KB Compressed size 162 MB 83 MB 1.92 MB 2.32 MB 314.5 KB Compression percentage 77 74.7 56.6 30 51.2 Effects of compression by percentage Compressing versus Compacting These two operations are conceptually similar in that each can result in more compact storage, but as applied to file geodatabases, these are two unrelated operations. Compaction n Tidies up the storage of records in files by reordering them and eliminating free space n Is recommended if data is frequently added and deleted n Can reduce file sizes and improve performance n Does not affect read/write capability n Should be performed regularly Compression n Reduces storage requirements n Improves database performance n Makes database or feature classes read-only n Should be performed as needed www.esri.com ArcUser Spring 2009 15