Yes, I know it's big. I think part of the problem is I put all my data in 1 geodatabase instead of smaller ones. Included in the database are: 1) Facility Points (1 feature class per year, 8 years), 2) geographic boundary files for the whole U.S. (counties, states, block groups), 3) associated geographic centroids (block groups only), 4) Service Areas broken into 3 travel zones (0-10, 10-30, 30-60 min) for ~4,000 facilities, 5) tables with attributes for these facilities, and 6) various spatial joins of the previously listed feature classes (the biggest of which has about 1.5 million records, i.e., attributes of block groups that fall within these service areas). The database is so big I can't copy it to a local drive (not enough space). It's all on a network drive.
And exporting some of the data to a different geodatabase is hard too, given the slowness (or crashes) I'm experiencing.
- Jan