Specifies the type of database management system to which a connection to create a geodatabase will be made.
The name of the instance.
For SQL Server, provide the SQL Server instance name. Case-sensitive or binary collation SQL Server instances are not supported.
For Oracle, provide either the TNS name or the Oracle Easy Connection string.
For PostgreSQL, provide the name of the server where PostgreSQL is installed.
The name of the database.
This parameter is valid for PostgreSQL and SQL Server. You can provide either the name of an existing, preconfigured database or a name for a database that the tool will create.
If the tool creates the database in SQL Server, the file sizes will be either the same as defined for the SQL Server model database or 500 MB for the .mdf file and 125 MB for the .ldf file, whichever is greater. Both the .mdf and .ldf files are created in the default SQL Server location on the database server. Do not name the database sde.
If the tool creates the database in PostgreSQL, it uses the template1 database as the template for the database. If you need to use a different template—for example, you require a template that is enabled for PostGIS—you must create the database before running this tool and provide the name of the existing database. Always use lowercase characters for the database name. If you use uppercase letters, the tool will convert them to lowercase.
Operating System Authentication
Specifies the type of authentication that will be used for the database connection.
The database administrator user for database authentication. For Oracle, use the sys user. For PostgreSQL, specify a user with superuser status. For SQL Server, specify any member of the sysadmin fixed server role.
Database Administrator Password
The database administrator password for database authentication.
Sde Owned Schema
This parameter is only active for SQL Server and specifies whether the geodatabase will be created in the schema of the sde user or in the dbo schema in the database. .
The name of the geodatabase administrator user.
If you are using PostgreSQL, this value must be sde. If the sde login role does not exist, this tool will create it and grant it superuser status in the database cluster. If the sde login role exists, this tool will grant it superuser status if it does not already have it. The tool also creates an sde schema in the database and grants usage on the schema to public.
If you are using Oracle, the value is sde. If the sde user does not exist in the Oracle database, the tool will create it and grant it the privileges required to create and upgrade a geodatabase and disconnect users from the database. The tool also grants privileges to allow data imports using Oracle Data Pump. If the sde user exists, the tool will grant these same privileges to the existing user.
Creating or upgrading user-schema geodatabases in Oracle is no longer supported.
If you are using SQL Server and specified an sde-schema geodatabase, this value must be sde. The tool will create an sde login, database user, and schema and grant it privileges to create a geodatabase and remove connections from the SQL Server instance. If you specified a dbo schema, do not provide a value for this parameter.
Geodatabase Administrator Password
The password for the geodatabase administrator user. If the geodatabase administrator user exists in the database management system, the password you provide must match the existing password. If the geodatabase administrator user does not exist, provide a valid database password for the new user. The password must meet the password policy enforced by the database.
The password is an encrypted string.
The name of the tablespace.
This parameter is only valid for Oracle and PostgreSQL database management system types. For Oracle, do one of the following:
This tool does not create a tablespace in PostgreSQL. You must either provide the name of an existing tablespace to be used as the database's default tablespace or leave this parameter blank. If you leave the parameter blank, the tool will create a database in the pg_default tablespace.
The keycodes file that was created when ArcGIS Server was authorized. If you have not done so, authorize ArcGIS Server to create this file.
This file is in the <drive>\Program Files\ESRI\License<release#>\sysgen folder on Windows or the /arcgis/server/framework/runtime/.wine/drive_c/Program Files/ESRI/License<release#>/sysgen directory on Linux.
The /.wine directory is a hidden directory.
You may need to copy the keycodes file from the ArcGIS Server machine to a location that is accessible to the tool.
Specifies the spatial type that will be used. This is only applicable to PostgreSQL databases.
|Create Enterprise Geodatabase Succeeded|
Specifies whether the enterprise geodatabase was successfully created.