On a certain server, the geoprocessing tool 'Create Enterprise Geodatabase' fails to create a SDE-schema geodatabase (with any name) when a database named 'SDE' already exists.
Last Published: August 25, 2014No Product Found
Bug ID Number
NIM077132
Submitted
January 18, 2012
Last Modified
June 5, 2024
Applies to
No Product Found
Version found
10.1
Status
Will Not Be Addressed
The development team has considered the issue or request and concluded it will not be addressed. The issue's Additional Information section may contain further explanation.
Additional Information
No Public Explanation
Workaround
1. Temporarily rename the SDE database to another name.2. Create the new geodatabase using the geoprocessing tool.3. Rename the old SDE database back to 'SDE'.*Use SQL Server tools such as SQL Server Management Studio to rename the database. Important! The SDE database cannot be used while it has been renamed. If the SDE database is part of a multiple-database model geodatabase which includes other databases, none of the member databases can be used while the SDE database is renamed. Be sure that no users are connected to the SDE database (and for MDM-GDB, other member databases) while the SDE database is renamed.