![]() Because geodatabase login roles likely do not exist yet, this tool grants usage to public. Login roles that will use the geodatabase must be able to access the sde schema. It sets the sde user as the owner of the sde schema and grants usage on the sde schema to the public role.The geodatabase system tables, views, functions, and procedures are stored in the sde schema. It creates an sde schema in the database.The sde user must be a superuser to create the geodatabase. ![]() You cannot use an operating system-authenticated sde login at this release. It creates a database-authenticated sde login role in the database cluster and grants it superuser status.When you run the Create Enterprise Geodatabase tool or script, specify the name of the database you created from a different template. If you need to create the database using a different template-for example, if you want to use the postgis template-you must create the database before running this tool. It creates a database using the PostgreSQL default template (template1).The following describes what the Create Enterprise Geodatabase tool does and the settings it uses: To achieve this, specific default settings are used. The Create Enterprise Geodatabase tool creates the database objects necessary for the geodatabase and grants required privileges for you. If you perform the role of both the database administrator and geodatabase administrator and, therefore, know the password for both login roles, you can use the Create Enterprise Geodatabase geoprocessing tool or a Python script that calls the tool to create a geodatabase in PostgreSQL. You are the PostgreSQL and geodatabase administrator If the database administrator and geodatabase administrator are two different people, follow the instructions for the PostgreSQL administrator to create the database and the geodatabase administrator to create the geodatabase.If you are the PostgreSQL database administrator and the geodatabase administrator, follow the instructions in the next section.Follow the instructions that apply to your situation: Determine who will create the geodatabase, because that affects who creates the database and which tool you use.Obtain an ArcGIS Server keycodes file and place it in a location you can access from the ArcGIS client you'll use to create the geodatabase.Confirm the ArcGIS, PostgreSQL, and operating system combinations you want to use are supported.For example, you can place the frequent access indexes or tables on devices that perform very fast e.g., solid-state devices, and put the tables containing archive data which is rarely used on slower devices. ![]() Second, you can use statistics to optimize database performance.First, if a partition on which the cluster was initialized is out of space, you can create a new tablespace on a different partition and use it until you reconfigure the system.There are two main advantages of using tablespaces: ![]() Tablespaces allow you to control the disk layout of PostgreSQL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |