Is This Content Helpful?
We're glad to know this article was helpful.
Instructions provided describe how to migrate from the multiple to single database model for Microsoft SQL Server Enterprise geodatabases. Geodatabases created at version 8.3 are under what is known as the multiple database model. This includes a SDE database where repository information is stored and one or more user databases. These user databases are used to store geographic data by storing the business, F, S, and i tables, while the SDE database stores the repository information (metadata) for the spatial data. The combination of the user database along with the SDE repository database collectively make up an ArcSDE geodatabase.
While it is possible to still have the multiple database model at version 9.0 and greater, this is not the default. ArcSDE 9.0 geodatabases created by the post installation wizard are created to be self contained under the single database model. This means that each database contains the business, F, S, i, and all of the repository tables. Each database also has a unique service pointing to it that runs on a unique port number.
To read more about the multiple and single database models, see the Related Information section at the bottom of this page.
Migration from Multiple to Single database model:
An issue exists with a change in architecture that manifests when users switch over and migrate to the new single database model. Since the geodatabase is split among multiple SQL Server databases, it requires that certain steps be taken to re-organize tables within the database.
There are two known methods for migrating between database models.
It is always suggested that a full database backup of all ArcSDE databases occurs before performing any type of change within a database schema.