ArcGIS 9.2 and later supports three types of geodatabases:
ArcSDE geodatabases An object-oriented geographic database that provides services for managing geographic data. These services include validation rules, relationships, and topological associations. A geodatabase contains feature datasets and is hosted inside of a relational database management system. (See also: personal geodatabase)., which are designed for multi-user environments and which Scenario 360 can use for source data;
Personal geodatabases A geodatabase stored in Microsoft Access database format that supports many readers and a single editor. See also: geodatabase., which were the primary type of single-user geodatabase from ArcGIS 8.0 to ArcGIS 9.1 but which have limitations on size (2GB) and stability; and
File geodatabases A type of geodatabase used by ArcGIS in versions after 9.1 and in Scenario 360 in versions after 3.2., which were introduced with ArcGIS 9.2 and are recommended as the primary format for data stored in a file system folder going forward. File geodatabases have the ability to handle far larger datasets (1TB per dataset) than personal geodatabases and are expected to be more stable and possibly faster.
Earlier versions of Scenario 360 (2.0 – 3.2) exclusively used personal geodatabases for dynamic data. Starting in Scenario 360 version 3.3, both personal geodatabases and file geodatabases are supported, and you can migrate any personal geodatabase-based analysis to file geodatabase format on command. However, once an analysis has been converted to file geodatabase format:
it cannot be converted back to personal geodatabase format, and
other users who have earlier versions of Scenario 360 (3.2 or earlier) or ArcGIS (9.1 or earlier) will not be able to open it.
To convert a personal geodatabase formatted analysis to file geodatabase format:
a.) Click “Yes” when prompted when you first open the analysis,
<OR>
b.) From the Scenario 360 toolbar menu drop-down list, choose Analysis > Convert to File Geodatabase.
Personal geodatabases have a 2GB size limit. Personal geodatabases may have ESRI geodatabase topology, but at the ArcView level, topology rules cannot be created or modified and feature classes involved in topology cannot be edited. Copying and pasting features into dynamic data layers (from non-dynamic layers) to create distinct scenarios may cause topology problems such as overlapping polygons and associated sliver polygons.
The personal geodatabases used by ArcGIS perform better and take up less space if they are periodically compacted. We recommend compacting your analysis geodatabase every few times you open it. You may use the Compact tool in the ArcGIS Toolbox under Data Management Tools/Database.
Scenario 360 supports ArcSDE (the gateway to server-based enterprise GIS) data sources. No special setup is required to take advantage of ArcSDE data. Scenario 360 works in both desktop and server environments, breaking the desktop size barrier and providing the ability to use larger study areas, more detailed analyses, and easier integration with existing geospatial DBMS environments.
For more information, see ArcMap help.