I'm looking for success stories about using an enterprise geodatabase (postgres) to store raster data. I mean not just for read-only access but also to write rasters out of geoprocessing tools (python, modelBulder, etc) directly to the enterprise gdb. I'm aware this is not a common approach, but I'm trying find all possible alternatives.
Is there any performance tips or tuning options that would allow the gdb to store and query the rasters with a performance somehow similar to what would be exprerienced using file gdbs to store the data?
Thanks in advance,