SDE multi-tablespace Management

The following section uses Oracle10g as an example to describe how to use SDE to manage multiple tablespaces and how to store different data under the corresponding tablespaces.

When using SDE to manage large amounts of data, you can first classify the data type and usage, and then store them in different tablespaces; this not only makes reasonable planning and classification of managed data, but also effectively reduces the load of Sde because these tablespaces can be centrally managed by SDE users.

 

• Create a tablespace for storing data

Create a tablespace lgydata to store data in Oracle.

• Modify dbtune table parameters

As shown in, when copying data to SDE in arccatalog, the data enters the tablespace with the config. Keyword column "defaults" by default, that is, the default table space of Sde. As long as you create the klgydata keyword in SDE and establish its association with the lgydata tablespace, you can use SDE users to manage the lgydata tablespace.

Open the SDE. dbtune table through the Oracle10g client or PL/SQL, as shown in. The keyword "ults" corresponding to the SDE tablespace is described in detail in the dbtune table, including related parameters. Therefore, the klgydata keyword is created in SDE, you only need to create the parameter expression information of klgydata in the dbtune table according to the defaults parameter format and content.

Use the SQL statement [Create Table SDE. dbtune123 as select * From SDE. dbtune where keyword = 'default'] creates a dbtune123 table. The table has the same structure as the dbtune table, but only contains the defaults parameter information.

Use the SQL statement [update SDE. dbtune123 set keyword = 'klgydata'] to update the keyword column value to "klgydata ".

The most important step is to modify the value of the config_string column. Because the configults keyword config_string column information is created when the SDE tablespace is created, it is associated with the SDE tablespace by default, so there is no tablespace information in its information. As shown in

The klgydata keyword was created later. Therefore, the tablespace information needs to be added to the config_string column of its parameter information. As shown in

Use the SQL statement [update SDE. dbtune123 set config_string = Concat ('tablespace lgydata', to_char (config_string) where substr (to_char (config_string),) = 'pctfree'] updates the value of the config_string column.Note: not all config_string column values need to be updated. You only need to update the columns whose values start with pctfree.

Use the SQL statement [INSERT INTO SDE. dbtune select * From SDE. dbtune123] to import the information in the dbtune123 table to the dbtune table.

By this step, the dbtune table has been modified to allow SDE users to manage multiple tablespaces.

• SDE users manage multiple tablespaces

Copy Data to SDE under arccatalog, as shown in figure

Import data to SDE under arccatalog, as shown in figure

The imported data tables are all in the lgydata tablespace.

Open the connection with the SDE user under arccatalog. Through this connection, you can see the data in the lgydata tablespace.

• Conclusion

SDE users can manage multiple tablespaces