Original User: erictrice
Hi Jamal,
1. Raster Catalogs and Mosaic Datasets can be used for managing very large collections of imagery, on the order of 1000's of TB's. With this in mind they were created with some built in visibility rules, so as to avoid the display hit (performance issue) one might take while trying to render so much data at one time. Because a single raster datasets size is highly unlikely to exceed that of a medium/large raster catalog or mosaic datasat, it doesn't need to have built in restrictions for displaying it.
2. I'm not sure I understand the issue you describe.
3. Raster datasets within raster catalogs can be managed in two ways by the file and personal geodatabases: either managed by the geodatabase or not. The default behavior is that the datasets are managed by the geodatabase. This means that when you load the catalog, the input rasters are converted and stored inside the geodatabase. If you chooose to not have the geodatabase managed the data, you select "Unmanaged" for the Raster Management Type parameter in the Create Raster Catalog tool. What this means, is the source rasters will be referenced from their original location and no data conversion or loading will ocurr. Mosaic datasets do not give you a choice; they are always unmanaged in the sense that they just point to the real data. If you change your catalogs in the future to be unmanged, they will load a lot faster and be more on par with what you see when loading a mosaic dataset.
4. I believe Melanie answered this question in another forum thread you posted it in. Nonethelss, nothing about the resolution is changing. It appears to be related to statistics and stretching. Did you try what she suggested? i.e. Settting the stretch type to None. If you zoom all the way in do they look the same?