Does any body knows the st_geometry storage requeriments vs sdeBinary storage requirements in Oracle?
In theory, the LONG RAW storage used with SDEBINARY should be about the same as the BLOB space used by ST_GEOMETRY, except:
Given the state of modern disk storage, you could probably store ten times the previous vector data in under $120 of disk (and it might have a faster seek time), so shoehorning datasets into disk shouldn't be a major concern.
Best practice would be create a new table in a new tablespace (tablespaces, if you consider indexes), taking the opportunity to spatially defragment the table(s) by using the Sort (Data Management) tool to optimize the draw performance by using a UL spatial sort option (Advanced [ArcInfo] license only) when populating the new table (Standard and Basic licenses would need to use a spatially correlated attribute, like zipcode, or mgrs, or geohash, or an index grid id to achieve spatial defragmentation).
Could you be more specific on what you are looking for when you say "storage" requirements?
I want to know if I will need more storage space in Oracle when I migrate from sdeBinary to st_geometry
Thanks a lot for your help
Retrieving data ...