Multiple geodatabases in one instance of SQL Server

If you want to create more than one geodatabase in the same SQL Server instance, you create multiple SQL Server databases, create a geodatabase in each one, authorize each geodatabase, and create separate ArcSDE services for each one (if you will be using ArcSDE services to connect to the geodatabases).

The following graphic illustrates that there are two separate databases, Database1 and Database2, on one SQL Server instance and that each database contains a complete geodatabase.

The databases can have any unique name that follows SQL Server rules for identifiers, does not start with a number, and is not sde.

You can use the ArcSDE for SQL Server Post Installation wizard to create additional databases and geodatabases. Run through all steps of the Post Installation wizard, making sure to provide a unique database name, ArcSDE service name, and ArcSDE service number. Since users are created at the instance level then added to the database in SQL Server, be sure to use the same password for the ArcSDE administrator when prompted.

If clients only use direct connections to each separate geodatabase, you do not need to create an ArcSDE service and can skip the last step of the Post Installation wizard. However, if clients connect using an ArcSDE service, you must create an additional service for each additional geodatabase. As mentioned, this can be done through the Post Installation wizard; just be sure to specify a different service name, port number, and the correct database name on the ArcSDE service information dialog box.

Be aware that if you plan to use different settings in the dbtune.sde, giomgr.defs, or dbinit.sde files, these changes must be made before running the Post Installation wizard.

• To specify different geodatabase storage information for the second geodatabase, make copies of your giomgr.defs and dbtune.sde files, giving them different names. For example, you could name them giomgr2.defs and dbtune2.sde. Alter the contents of these new files. When you run the Post Installation wizard, you will specify these custom files.
• To set variables in the dbinit.sde file to connect to the second geodatabase, make a copy of your dbinit.sde file, giving it a new name. This name must include the name of the new ArcSDE service. For example, if the new service name is sdesql2, name the dbinit file dbinit_sdesql2.sde. Add the appropriate variables to the new dbinit file. When running the Post Installation wizard, specify the new dbinit file.

Client connections can be made to one geodatabase at a time. When connected to one single spatial database geodatabase on a SQL Server instance, you cannot query information from another geodatabase on the SQL Server instance through that same connection.

For instance, in ArcCatalog, you could create a spatial database connection to Database1. When you add data to ArcMap through that connection, you cannot view the data in Database2. To access the data in Database2, you would set up a second spatial database connection in ArcCatalog, this time specifying Database2 in the Database field and Database2's port number in the Service field.

For information on setting up spatial database connections in ArcCatalog, see Making ArcSDE service connections from ArcGIS Desktop to a geodatabase in SQL Server. For making direct connections, see Making a direct connection from ArcGIS Desktop to a geodatabase in SQL Server.

Legacy:

At ArcSDE 9 and later releases, two different data storage models are supported for SQL Server: multiple and single spatial database models. Prior to ArcSDE 9, only the multiple spatial database model was available. Though still supported, the multiple spatial database model has been deprecated. See The SQL Server multiple spatial database model if you want to see a discussion of this type of geodatabase.