Dbms2sde Performance Boosters

Running dbms2sde with -load and -buffer are optional, but together they result in tremendous (e.g., 35-fold) improvements in processing time. The following table shows the time (in minutes and seconds) dbms2sde took to spatially enable 10,000 rows using the various combinations of storage type and -load and -buffer options.

^*Time in minutes and seconds to spatially enable 10,000 rows.

2-table means that a copy of the original business table is spatially enabled. 1-table means the original business table is spatially enabled. There is no 1-table mode for the SDO_GEOMETRY storage type (native SQL) because of a bug in ArcSDE that prevents the creation of a spatial layer on a non-empty business table using the SDO_GEOMETRY storage type.

The -buffer option cannot be used in 1-table mode because buffering is applicable only for table inserts and not table updates (in 1-table mode rows are updated with shape information, in 2-table mode new rows—with shape information—are inserted into the copied table).