For spatial database with raster support you can use any of the following, depending on your requirements:
PostGIS Raster: From their website - "PostGIS Raster is an
ongoing project aiming at developing raster support in PostGIS. It is
a new project very different from the previous PGRaster project and
also very different from Oracle Spatial GeoRaster.
The goal of PostGIS Raster is to implement the RASTER type as much as
possible like the GEOMETRY type is implemented in PostGIS and to
offer a single set of overlay SQL functions (like ST_Intersects)
operating seamlessly on vector and raster coverages.
PostGIS Raster will be integrated part of the future release of
PostGIS 2.0 (spring 2012)!"
Although this is still under development, you can give it a try as this is open source, easy-to-use with GUI pgAdmin and offers lot of spatial functionalities.
- RasterLite: A very simple C library implementing an efficient
storage solution for huge raster data sources based on SQLite +
SpatiaLite Spatial DBMS. You can find the manual here.
This might be worth looking at as a light-weight alternative. This is also open source.
There may exist other options, too. However I personally feel, unless you are going to use any spatial functionalities for your raster data directly through build-in functions of the spatial database, it is always better to keep your raster data in file structure and save the path in your database. This will reduce your retrieval time, as well as improve your performance. Although there are limitations in this approach, you can easily deliver your data through LAN using a server side scripts.