Do you have an adequate amount of free space within your tablespace? If your tablespace needs to allocate more space for each raster load, this will slow down the process. Also, is there any type of compression applied to the raster? You can check this by right-clicking on the raster > Properties. Here you can also check the 'Uncompressed Size'. Is this also 100 MB?
Hi Karthik,Are you uploading one IMG or are you mosaicking multiple IMGs into a single raster dataset within the SDE geodatabase?
There's a huge number of variables that go into raster loading performance. Some of themare under your control (like the Oracle tuning and compression options) some not (like theperformance of the 9.2 raster processing libraries). There have been three significant changeswith recent (10.x) ArcGIS products: Incorporation of the GDAL raster libraries, the use of ArcGIS Server caches, and the use 9.2 Image Server technology into the ArcGIS productbase. Each of these weakened the use of rasters within database; taken together, theyhave effectively eliminated the need to load raster data into databases at all. While youprobably have some room for database tuning (which would require starting the load overagain), I can't help but wonder if you should reevaluate the long-term effectiveness of your task.- V
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
