Your existing raster datasets that have been created with the ArcSDE binary type can be converted to the ST_Raster type using the Migrate Storage geoprocessing tool or a Python script.
During migration, a new ST_Raster column is added to the business table, and the raster band metadata stored in the SDE_BND_<N> raster band table is extracted and written in the ST_Raster column. The original integer raster column is then dropped, and the new ST_Raster column is given the original raster column name. The raster band table is also dropped.
In most cases, the conversion from binary to ST_Raster will be fast with a relatively low impact on the system. This will be true for all but two cases: converting raster data stored as Oracle LONG RAW and converting raster data stored in a SQL Server image type column.
For the Oracle case, the LONG RAW BLOCK_DATA column in the raster blocks table (SDE_BLK_<N>) must be converted from LONG RAW to BLOB before the conversion to ST_Raster can be completed. For the SQL Server case, the image BLOCK_DATA column in the raster blocks table (SDE_BLK_<N>) must be converted to a varbinary column.
Always make a backup of the geodatabase before you migrate data.
Compress the geodatabase
The geodatabase administrator can compress the geodatabase using the Compress command in ArcGIS for Desktop. See Compressing an enterprise geodatabase for instructions.
Create a database backup
The database administrator should create a backup of the geodatabase before you migrate any data. That way, if migration fails or you decide you don't want to use the new data, you can go back to the original data.
The migration process is designed to be recoverable. If it fails for any reason, correct the problem that caused the failure and rerun the migration. If for some reason you are unable to complete the migration at that point, you can restore the data from the backup.
Install the ST_Raster type
Before you can migrate your raster columns to the ST_Raster type, you must configure your geodatabase to store ST_Raster by running the sdesetup command with the install_st_raster operation. See the topic that is appropriate to your installation:
Migrate one raster catalog, raster dataset, mosaic dataset, or table or feature class containing a raster field at a time.
You must be the owner of the dataset to migrate it to a different storage type.
Set the RASTER_STORAGE parameter
You must have the RASTER_STORAGE parameter set to ST_Raster in one of your configuration keywords. That keyword is then specified when you run the Migrate Storage tool or script.
Do one of the following to add the RASTER_STORAGE parameter and set it to ST_RASTER:
- Set the RASTER_STORAGE parameter under the DEFAULTS configuration keyword to ST_RASTER.
- Create a custom configuration keyword that contains, at a minimum, the RASTER_STORAGE parameter set to ST_RASTER and a UI_TEXT parameter.
Now run the Migrate Storage geoprocessing tool to migrate raster catalogs or datasets.
Run the Migrate Storage tool
You can run the Migrate Storage geoprocessing tool on a group of raster catalogs, raster datasets, mosaic datasets, or tables or feature classes containing raster fields. Or you can script the migration in Python to serially migrate a group of files.
- In ArcCatalog or the Catalog window in ArcMap, search for the Migrate Storage geoprocessing tool, which is in the Data Management toolbox.
- Provide the information required by the tool. This includes the path to and name of each raster catalog or dataset and the configuration keyword to use for the migration.