ArcSDE 10.1 for Windows creates a spatial database with common errors _sql Server

This is the 2013 time that I took part in the ESRI contest, when I created the ARCSDE 10.1 for SQL Server, so I wrote the document.

Having been busy studying, forgot to publish. Today I have the same problem, I think many people may have encountered the problem,

So share with you, please criticize correct.

1. Create Geodatabase 1.1, open the Geodatabase administration tool

Added the Geodatabase administration (geodatabaseadministration) toolset in the Toolbox, which contains several tools for geodatabase administration operations, as shown in:

1.2. Create an Enterprise Geodatabase

Double-click to open the Create Enterprise Geodatabase tool and enter the parameters as shown in:

Parameter description:

Database platform: This article chooses Sql_server, has no controversy;

instance: The SQL Server instance name needs to be filled in, this article is "localhost";

Database: Geodatabase name, the default is SDE, you can also fill in other names such as: "Sde1" in this article;

Authorization file: An authorization file, an. ecp file, which is the same as the authorization file for ArcGIS server;

The other is to enter the password for the database administrator, the Geodatabase administrator.

After setting the parameters, click "Confirm" to start creating the geodatabase, this process is equivalent to the original post Install, will create the SDE system table and so on.

After the creation is complete, you can view the results in SQL Server Management Studio, such as:

If the parameters are set correctly, you can see that the database has more than one SDE library, including the SDE system table. If an error occurs, the database connection configuration needs to be checked in addition to the input parameters, the license file,

1.3 Common Database Connection errors

Such as:

1.3.1, SQL Server version inconsistency

If the database server is loaded with SQL Server2008 R2 Enterprise Edition and is a SP3 patch, and I am a SQL Server Express on the client, and there is no patching, the connection will fail, and the geodatabase creation will fail naturally. It is therefore necessary to ensure that the client and server versions of SQL Server are consistent and can be successfully connected.

1.3.2, did not hit the ArcGIS Desktop SP1 patch

If the server has SQL Server 2012 installed, you will need to hit the ArcGIS Desktop SP1 patch, or else the above error is reported. (This problem was discovered only by the brother's guidance)

1.3.3 Instance Name error

Online bloggers fill in the form such as: "Server name/sql Server instance name", but I tried, always reported access to the DBMS server failed, but the ArcGIS10.1 help document is also required to fill this. If you fill in the parameters as a help document, the result is still unsuccessful. Recommended to try, directly fill in the server name, I have tested, can be successfully created.

2. Connection

The Geodatabase has been created successfully, and then you can connect to the Geodatabase. Direct Connect is recommended in ArcGIS 10.1, so the SDE system service is not created by default.

2.1. Direct Connect

Direct Connect is simple, under database connections, double-click Add Database connection, such as:

Pop up the Direct Connect parameter Settings window and set the direct connection parameters, such as:

Note the instance here, and the need to create a geodatabase consistent, and then select the Geodatabase to connect to, enter the user password, click OK, you can connect, such as:

Now it's empty, and then we'll test the Shapefile feature class into this SDE library with the following results:

Indicates that the direct Connect method is already working with the ARCSDE library.

2.2. Service Connection

In addition to the recommended direct connection, there are times when we need to create an ARCSDE service and then connect to the Geodatabase in the same way that the. SDE connection file is used by the client.

2.3. Create an ARCSDE service

There are three main steps to creating an ARCSDE service: Manually modifying Service files, command-line installation Services, and starting services.

The first is to manually modify the service files, including the ArcSDE service.sde files and the Windows system service files, as in the following two graphs:

To change the services file, the file path is as follows:

C:\Windows\System32\Drivers\etc

In these two files, add "Esri_sde 5151" separately and save as shown in:

Then use the command line to create the ARCSDE service, this example command line is as follows:

Sdeservice-o create-d sqlserver,localhost-psde-i Esri_sde

The execution results are as follows:

After the creation is successful, the service can be started with the following command line:

Services.msc

After execution, you will be asked to enter the SDE user password, which can then be started, as shown in:

The SDE service is started and can then be connected by service mode.

2.4. Create a Service connection file

First find the Create ARCSDE Connection file tool, as shown in:

Open the tool and enter the parameters as shown in:

Here you need to set the machine name or IP where the SDE service resides (in this case, localhost), the SDE service name (in this case, ESRI_SDE or 5151), and enter the database name (in this case, SDE) and the username password.

Click "Confirm" to complete the creation of the. SDE Service connection file, locate the connection file under the specified directory, and double-click to connect to the Geodatabase as shown (the data imported in the direct-attached test is clearly visible):

Explains how the service connection is working correctly with the ARCSDE library.

Thursday, July 18, 2013

Jxust GIS Laboratory Fire boat

ArcSDE 10.1 for Windows creates a spatial database with common errors _sql Server