Modifying configuration keywords in SQL Server

Доступно с лицензией Production Mapping.

Когда файлы данных будут созданы, введите новое ключевое слово конфигурации в таблице DBTUNE. На основе этого нового ключевого слова, данные и объекты базы данных будут сохранены в местоположение FileGroups, которое было задано ранее. Таблица DBTUNE хранится в базе геоданных на SQL Server. Чтобы изменить DBTUNE, необходимо экспортировать DBTUNE в текстовый файл и произвести изменения в данном текстовом файле. После внесения обновлений в текстовый файл, импортируйте новый DBTUNE из текстового файла.

Примечание:

При копировании и вставке примеров могут возникнуть синтаксические ошибки.

1. Export the dbtune file before making any modifications.
   1. Start ArcCatalog.

      Подсказка:

      You can also export using ArcMap.

   2. Click the ArcToolbox button on the Standard toolbar.
   3. Expand Data Management Tools > Geodatabase Administration..
   4. Double-click Export Geodatabase Configuration Keywords.

      The Export Geodatabase Configuration Keywords dialog box appears.

   5. Click the browse folder for the Input Database Connection parameter and browse to the connection file for the enterprise geodatabase you want to export.
   6. Click the browse folder for the Output File parameter and browse to the path where the file will be exported.
   7. Name the file dbtune_exp.txt and click Save.
   8. Click OK on the Export Geodatabase Configuration Keywords dialog box.
2. Copy dbtune_exp.txt to dbtune_<Database Name>.txt.
3. Using a file-based editor, modify the ##DEFAULTS configuration keywords to control in which FileGroup the tables and indexes will be created.

   Примечание:

   If your geodatabase only stores the product library workspace, the dbtune_<Database Name>.txt file can be opened in a text editor where you can manually edit the ##DEFAULTS configuration keyword; otherwise, create a new configuration keyword using the following example.

   dbtune_prodlib.sde
   
   ##DATA_DICTIONARY
   B_CLUSTER_ROWID            0
   B_CLUSTER_USER             0
   B_INDEX_ROWID              "WITH FILLFACTOR = 75 ON PRODLIB_SDEDICTINDEX"
   B_INDEX_USER               "WITH FILLFACTOR = 75 ON PRODLIB_SDEDICTINDEX”
   B_STORAGE                  "ON PRODLIB_SDEDICT"
   I_STORAGE                  "ON PRODLIB_SDEDICT"
   MVTABLES_MODIFIED_INDEX    "WITH FILLFACTOR = 75 ON PRODLIB_SDEDICTINDEX”
   MVTABLES_MODIFIED_TABLE    "ON PRODLIB_SDEDICT"
   STATE_LINEAGES_INDEX       "WITH FILLFACTOR = 75 ON PRODLIB_SDEDICTINDEX”
   STATE_LINEAGES_TABLE       "ON PRODLIB_SDEDICT"
   STATES_INDEX               "WITH FILLFACTOR = 75 ON PRODLIB_SDEDICTINDEX”
   STATES_TABLE               "ON PRODLIB_SDEDICT"
   VERSIONS_INDEX             "WITH FILLFACTOR = 75 ON PRODLIB_SDEDICTINDEX”
   VERSIONS_TABLE             "ON PRODLIB_SDEDICT"
   XML_INDEX_TAGS_INDEX       "WITH FILLFACTOR = 75 ON PRODLIB_SDEDICTINDEX”
   XML_INDEX_TAGS_TABLE       "ON PRODLIB_SDEDICT”
   END
   
   ##DEFAULTS
   A_INDEX_RASTER	"WITH FILLFACTOR = 75 ON PRODLIB_AINDEX"
   A_INDEX_ROWID	"WITH FILLFACTOR = 75 ON PRODLIB_AINDEX"
   A_INDEX_SHAPE	"WITH FILLFACTOR = 75 ON PRODLIB_AINDEX"
   A_INDEX_STATEID	"WITH FILLFACTOR = 75 ON PRODLIB_AINDEX"
   A_INDEX_USER	"WITH FILLFACTOR = 75 ON PRODLIB_AINDEX"
   A_INDEX_XML	"WITH FILLFACTOR = 75 ON PRODLIB_AINDEX"
   A_STORAGE	"ON PRODLIB_ADATA"
   B_INDEX_RASTER	"WITH FILLFACTOR = 75 ON PRODLIB_BINDEX"
   B_INDEX_ROWID	"WITH FILLFACTOR = 75 ON PRODLIB_BINDEX"
   B_INDEX_SHAPE	"WITH FILLFACTOR = 75 ON PRODLIB_BINDEX"
   B_INDEX_TO_DATE	"WITH FILLFACTOR = 75 ON PRODLIB_BINDEX"
   B_INDEX_USER	"WITH FILLFACTOR = 75 ON PRODLIB_BINDEX"
   B_INDEX_XML	"WITH FILLFACTOR = 75 ON PRODLIB_BINDEX"
   B_STORAGE	"ON PRODLIB_BDATA"
   D_INDEX_ALL	"WITH FILLFACTOR = 75 ON PRODLIB_DINDEX"
   D_INDEX_DELETED_AT	"WITH FILLFACTOR = 75 ON PRODLIB_DINDEX"
   D_STORAGE	"ON PRODLIB_DDATA"
   GEOMETRY_STORAGE	"GEOMETRY"
   S_INDEX_ALL	"WITH FILLFACTOR = 75 ON PRODLIB_SINDEX"
   S_INDEX_SP_FID	"WITH FILLFACTOR = 75 ON PRODLIB_SINDEX"
   S_STORAGE	"ON PRODLIB_SDATA"
   XML_DOC_INDEX              "WITH FILLFACTOR = 75 ON PRODLIB_XMLINDEX"
   XML_DOC_STORAGE            "ON PRODLIB_XMLDOC"
   XML_IDX_INDEX_DOUBLE       "WITH FILLFACTOR = 75 ON PRODLIB_XMLINDEX"
   XML_IDX_INDEX_ID           "WITH FILLFACTOR = 75 ON PRODLIB_XMLINDEX"
   XML_IDX_INDEX_PK           "WITH FILLFACTOR = 75 ON PRODLIB_XMLINDEX"
   XML_IDX_INDEX_STRING       "WITH FILLFACTOR = 75 ON PRODLIB_XMLINDEX"
   XML_IDX_INDEX_TAG          "WITH FILLFACTOR = 75 ON PRODLIB_XMLINDEX"
   XML_IDX_STORAGE            "ON PRODLIB_XMLINDEX"
   END
   

4. Import the modified dbtune_<Database Name>.txt file using ArcCatalog or ArcMap.
   1. In the ArcToolbox window, expand Data Management Tools > Geodatabase Administration.
   2. Double-click the Import Geodatabase Configuration Keywords tool.

      The Import Geodatabase Configuration Keywords dialog box appears.

   3. Click the browse button next to the Input Database Connection parameter and browse to the connection file for the enterprise geodatabase from which to import.
   4. Click the browse folder for the Input File parameter and browse to the path where the file will be imported.
   5. Name the file dbtune_<Database Name>.txt and click Open.
   6. Click OK on the Import Geodatabase Configuration Keywords dialog box.