Solved! Go to Solution.
There are probably a number of things going on here:
- Databases format differently than file geodatabase
- Databases index differently than file geodatabase
- File geodatabase supports compression
But first that are a number of issues to address:I'd expect a File Geodatabase to be faster (especially after you compress it) than any RDBMS-
- Are you using an Enterprise ArcSDE in the SQL-Server Express?
- What is the default storage format?
- How is your coordinate reference (specifically xyscale) defined?
- What is the physical size of the file geodatabase directory (according to Explorer)?
based geodata, so I'm wondering why you are even on this path. Do you really need multi-user
editing on a contours layer?
- V
Are you using Enterprise ArcSDE or Personal/Workgroup ArcSDE in the Express instance?
I think the default is now GEOMETRY storage, which would explain the significant storage
difference.
I think the default is now GEOMETRY storage, which would explain the significant storage
difference.
Are you using Enterprise ArcSDE or Personal/Workgroup ArcSDE in the Express instance?
- V