ArcSDE database architecture design

I don't know how to name a question. I am afraid that this name will be misunderstood. This document is intended to give some beginners how to organize SDE databases and user databases when using different databases, how multiple users operate on the same database, how their permissions are assigned, and so on. If the Oracle database is an Oracle database, after installing the ArcSDE software,

I don't know how to name a question. I am afraid that this name will be misunderstood. This document is intended to give some beginners how to organize SDE databases and user databases when using different databases, how multiple users operate on the same database, how their permissions are assigned, and so on. If the Oracle database is an Oracle database, after installing the ArcSDE software,

I don't know how to name a question. I am afraid that this name will be misunderstood. This document is intended to give some beginners how to organize SDE databases and user databases when using different databases, how multiple users operate on the same database, how their permissions are assigned, and so on.

Oracle Database

If the Oracle database is installed with the ArcSDE software and there is an SDE tablespace and SDE user in the database after the Post is complete, how should we store user data?

Method 1: Expand the SDE tablespace capacity, directly import user data to SDE users, or create a new user, but the default tablespace is SDE tablespace, and all data is poured into SDE tablespace.

Disadvantage: the user data and the SDE-related structure table are put in one piece. Obviously, the layers are not clear, and the user is prone to misoperations on the SDE-related structure table.

Method 2: This is the recommended method, as shown in. You can create a tablespace that stores your data, and then create one or more users that belong to the tablespace, this user gives connect and resource permissions. When a user uses ArcCatalog for user connection, user data is stored in the user's own tablespace, however, the related information (user data table name, table column name, data projection, and other information) is automatically registered to the SDE tablespace. You do not need to perform these steps, the relevant interfaces of ArcGIS products are automatically processed in the background. For Beginners, this method often makes them confused, I always feel that my data can be registered only in the SDE tablespace. It will be automatically registered in other tablespaces or additional operations are required, the user can perform the test according to the above explanation.

For multiple users in a tablespace, the permission problem can be solved by using the Oracle database, which has related permissions. However, ArcGIS can also be used to grant related permissions.

This feature can be found in the ArcToolbox tool or elsewhere. If it is the data owner, that is, the user who creates or imports the data, it can be assigned to other users to read (select) or write (Edit) permission. You can use this method to perform permission operations.

SQL Server database

For Oracle databases, we use a lot of data, but for SQL Server databases, you need to pay attention to some issues. Users who are used to Oracle databases may also like Oracle Data Organization when using SQL Server databases, that is, after the user installs the ArcSDE software and finishes the Post, the system will create an SDE database and an SDE user, so you can create a new database, then create a new database user, also use Oracle to import data, the data is stored in the new database, and the data information is registered in the SDE database. This is acceptable, but Esri does not recommend users to organize it at ArcGIS9.3, how can we reduce the efficiency? If you do not want to explain it, you can understand it. So all the above is nonsense.

Take a look at the figure above. For the SQL Server database, if the user is a database, we recommend that you put the user data together with SDE, that is, directly import it to the SDE database, if you want to store multiple databases separately, we recommend that you create an SDE Schema for each database, as shown below:

When creating a Database, modify the new Database name, and then create the corresponding ArcSDE service for each Database name. Which Database is connected during data connection, enter the corresponding name in the Database.

For SQL Server users, the SQL Server database has an sa user by default. This is the first user to create an ArcSDE database, and is also an SDE user at the operating system level, the SDE users of sa users are above all databases. These two users can connect to all SDE databases, as shown in the PPT. We can also create users for each database.

How can I create multiple users for the SQL Server database?

For SQL Server user creation, you only need to install the Wizard to create the user, but I also receive user consultation, after creating a new user, you can use the new user to connect, however, the following error occurs when you import data to a new user:

The cause of this error is: when creating a user, we cannot use the SDE Or DBO architecture. We need to create the user's architecture under the SDE database or a database with the SDE Schema, then select the architecture.

As shown in: I want to create another user except SDE In the Sde database, such as aaa. First, I need to create an aaa architecture.

Then, you can change the architecture of the created aaa user to that of the aaa user.

Http://blog.csdn.net/linghe301/archive/2011/02/14/6183962.aspx

The following describes how to name the imported data from SQLServer: database name. User Name. layer name, as shown below:

The intermediate name is SDE, which indicates that the SDE user has imported the data and the intermediate name is DBO. It indicates that it is a Sa user or another user but has sysadmin permissions, and others are imported by the common user.

Bytes -------------------------------------------------------------------------------------------------------

QQ Group 1: 78773981

QQ Group 2: 225989940
Blog: http://blog.csdn.net/linghe301
WEAVER: http://www.weibo.com/linghe301
Bytes -------------------------------------------------------------------------------------------------------