I have just realised that I will not have enough space on my harddrive to accomodate a raster which is being copied into an arcsde geodatadatabase. I am afraid, that if I stop the process in ArcCatalog, I will corrupt the raster in the geodatabase and not be able to delete it...or even worse corrupt the whole database.

Can anyone advise me on how to stop the copying process and ensure that the sde Geodatabase will not hold any remnants.

Arcsde9.3 / ArcCatalog 10.0 / MSSQL

1 Answer 1


You can kill the loading process on the client OS or kill the database session from the database.

The active raster being updated would likely be damaged, but you are unlikely to damage the geodatabase as a whole (certainly less so than letting the database overfill). Repair steps would be dependent on what kind of loading was being done.

It is no longer best practice to place rasters in ArcSDE, and well on the way to something which is not recommended. If you used mosaic datasets and the other raster advances in ArcGIS that resulted from integration of the former Image Server you wouldn't be running out of database storage.

  • Thanks for the comments. How should rasters be managed then? How else can I serve raster data in a arcgis server environment other than through an arcsde database? Commented Jan 14, 2014 at 15:03
  • Starting at 9.2, and running through 10.2, ArcGIS Server has received significant new capabilities in raster management with each release. The options with modern software are too broad to fit one of these tiny comment boxes. resources.arcgis.com/en/help/main/10.1/009t/…
    – Vince
    Commented Jan 14, 2014 at 15:28
  • Ok Thanks..I had to cancel the copy operation in ArcCatalog which seems to now be frozen. Any idea how I can now remove the corrupt data which I now have in MSSQL? Should I stop the ArcCatalog process...or will something be happening in the background? Any advice regarding repair steps to the mssql database? Commented Jan 14, 2014 at 15:35
  • forums.arcgis.com/threads/…
    – Vince
    Commented Jan 14, 2014 at 15:51
  • Oh well....Now I can´t connect to my sde Geodatabase...so I guess the whole GDB is now corrupt. Thats about 4 weeks of work out the window then! Commented Jan 14, 2014 at 16:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.