Configuring and Managing the Multiuser Geodatabase Student EditionCopyright © 2012 Essi All ights reserved, (Course version 1.1, Version release date June 2072 Printed in the United States of America ‘The information contained in this document is the exclusive property of Es, This work is protected under United States copyright law and other international copyright treaties and conventions. No part of this work may be reproduced oF transmitted in any form ox by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by Est. All quests should be sent to ‘Attention: Contacts and Legal Services Manager, Esr, 380 New York Street, Redlands, CA 92373-8100 USA, EXPORT NOTICE: Use of these Matarials is subject to U.S, export control laws and regulations including the US. Department cof Commerce Export Administration Regulations (EAR). Diversion of these Materials contrary to U.S. law i prohibited. ‘The information contained in this document is subject to change without notice. US Government Restricted/Limited Rights Any software, documentation, and/or data delivered hereunder is subject tothe terms of the License Agreement. ‘The commercial icense rights in the License Agreement strictly govern Licensee's use, reproduction, or disclosure of the software, data, and documentation. la no avent shall the US Governmant acquire greater than RESTRICTED/ LIMITED RIGHTS. Ata minimum, use, duplication, or disclosure by the US Government is subject to restrictions as set forth in FAR §52.227-14 Alternates II, and Il (DEC 2007); FAR §52.227-19(b) (DEC 2007) and/or FAR §12.211/ 12.212 (Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (DEC 2011) (Technical Data - ‘Commercial Items) and/or DFARS §227.7202 (Commercial Computer Software andl Commercial Computer Software Documentation), ae applicable, Contractor/Manufacturr is Esri, 380 New York Stet, Redland, CA 92373-8100, USA, @osri.com, 3D Analyst, ACORN, Address Codsr, ADF, AML, ArcAtlas, AreCAD, ArcCatalog, ArcCOGO, AreData, AvcD2e, ArcEdit, AcEcltor, ArcEurope, ArcExplorer, AreExpress, ArcGIS, ArcGlobe, ArcGrid, ArcIMS, ARCJINFO, Arcinfo, Arclafo Librarian, AvcLossons, Avclocation, Avclogistis, ArcMap, ArcNetwork, AreNews, ArcObjects, ArcOpen, ArcPad, ArePlot, ArcPress, ArcPy, ArcReader, ArcScan, ArcScene, AreSchool, ArcScripts, AreSDE, ArcSdl, AreSketch, ArcSto1m, AicSurvey, ArcTIN, ArcToolbox, ArcTools, ArcUSA, Arct/ser, AreView, AreVoyager, ArcWatch, ArcWeb, AreWerld, ArcXML, Atlas GS, AtlasWare, Avenue, BAO, Business Analyst, Business Analyst Online, BusinessMAP, CityEngine, Communitylnfo, Database Integrator, DBI Kit, EDN, Esi,Essi—Team GIS, Esti—The Gi5 Company, EssiThe GIS People, Esti—The GIS Software Leader, FormEdit, GeoCollector, Geographic Design System, Geography Matters, Geography Notwork, GIS by Esti, GIS Day, GIS for Everyone, GiSData Server, JTX, Maplt, Maplex, MapObjects, MapStudio, ModelBuilder, MOLE, MPS—Atias, PTS, Rent-a-Tech, SDE, SML, Sourcebook America, SpatiaL ABS, Spatial Oatabase Engine, StreetMap, Tapesty, the ARC/INFO logo, the AreIS logo, the ArcGIS Explorer loge, the ArcPad logo, the Esti globe logo, the Esri Press logo, the GIS Day logo, the Maptt logo, The Geographic Advantage, The Geographic Approach, The Werld's Leading Desktop GIS, Water Whtes, \yvearegis.com, wav. 0s¢ com, winw.geographynetwork.com, wuw.gis.com, wiw.gisday.com, and Your Personal Geographic Information System are trademarks, service marks, of registered marks in the United States, the European ‘Community, or certain other jurisdictions. CityEngine isa registered trademark of Procedural AG and is distributed uncor license by Es (thor companies and products or services mentioned herein may be tradematks, service marks or registered marks oftheir respective mark owners,w Course introduction Introduction Course goals Additional resources Installing the course data Using the geodatabase Lesson introduction Why use a geodatabase? Desktop format geodatabases ArcSDE technology geodatabases. Geodatabase workllow Exercise 1: Migrate to the geodatabase Explore data sources. Create a geodatabase Load data into the geodatabase ‘Administer the geodatabase Use the geodatabase Lesson review What is ArcSDE? Lesson introduetion Multtier architecture Identity the appropriate software ArcSDE components Administrative users Create and enable enterprise geodatabases Explore the repository. Exercise 2: Create an enterprise geadatabase. Verify requirements Create an enterprise geodatabase View the repository... Lesson review Connecting to the geodatabase Lesson introduction Direct connections, Application server connections. Connection considerations Choose a connection strategy. Creating direct connections Creating the ArcSDE service and connections Software version compatibility 14 12 13 14 15 7 18 ry 1-10 111 412 114 a4 32 33 34 34 35 36 341Modify the connection limit Exercise 3: Configure connections to a geodatabase Croate a direct connection. Configure the application server Connect using an application server. View connections Choose a connection strategy. Lesson review Loading data into the geodatabase Lesson introduction. Data owner account Create the data owner account. Geoprocessing environment settings. ROBMS considerations Choosing a dataloading tool Updating datasets Automation Using ModelBuilder. Exercise 4: Load data into the geodatabase Create the data owner account Load new datasets Update datasets. Lesson review Managing storage Lesson introduction Configuration parameters Configuration keywords . DBTUNE Create and update keywords. Exercise 5: Customize storago using configuration keywords. Investigate Help documentation Export DBTUNE, Edit the file Import DBTUNE Use the keyword to load data Lesson review Spatial types Lesson introduction AreSDE compres Spatial field types Supported spatial types cd binary 343 345 346 3.16 319 3.20 3.21 3.23 a 42 43 45 46 47 48 49 410 413 ata 44s ANG ang 54 53 55 59 5-10 5410 Bat 512 512 544 bt 4? 62 63Configuring spatial types Migrating spatial types. Exercise 6: Work with spatiel pes Load data using SQL Server Geography Migrate SDE binary data Lesson review Configuring permissions Lesson introduction Data users. Operating system users. Database users. Roles: Defining roles Design roles. Applying permissions. Securing credentials Exercise 7: Configure permissions for data use Design a role strategy Create roles and users Apply permissions. Tast permissions, Lesson review Associating data Lesson introduction Database views. Creating database views Determine when to create database views Query layers Creating query layers Exercise 8: Associate data with database views and query layers, Explore election data Create database views Use database views. Create a query layer. Lesson review Maintaining the qeodatabase Lesson introduction Autribute indexes. Creating and updating attribute indexes. Spatial indexes Statistics. 65 65 67 69 6-12 oa 72 73 73 7A 74 75 2 78 79 7-10 710 a 7.13 715 8-10 812 ot 92 93 98 9510 a Updating statistics. Scheduling tasks. Managing performance tasks with Python Exercise 9: Maintain performance in your geodatabase Create indexes Update indexes Update statistics. Automate performance tasks. Schedule the Python script Lesson review Managing geodatabase locks Lesson introduction Feature locks Schema locks: Viewing and clearing locks. Exercise 10: Identify and manage locks Explore feature locks. Explore schema changes. Disconnect users Lesson review. Geodatabase workflow Lesson introduction Geodatabase workflow. Geodatabase users. Geodatabase tasks. Exercise 11: Configure and manage a multiuser geocatabase. Create the Manhattan geodatabase.. Load data into the geodatabase Apply permissions. Maintain performance. Lesson review. Appendixes Appendix A: Esri data license agreement. Appendix B: Answers to lesson review questions 96 oF 98 99 9-10 oat oat oat 914 9.16 10-41 10-2 103 10-4 105 106 107 108 10-10 at 12 114 11s wa 18 18 18 Ws wet atLesson 1: Using the geodatabase. Ba Lesson 2: What is ArcSDE? 82 Lesson 3: Connecting to the yeolatabase. . 83 Lesson 4: Loading data into the geodatabase Ba Lesson 5: Managing storage. soe BS Lesson 6: Spatial types. sos 86 Lesson 7: Configuring permissions 87 Lesson 8: Associating data 88 Lesson 9: Maintaining the geodatabase Bo Lesson 10: Managing geodatabase locks. 8-10 Lesson 11; Geodatabase workflow 8-11Introduction This course prepares you to successfully deploy @ multiuser geodatabase to manage your organization's critical geographic data assets, You will learn about the multiuser geodatabase architecture and installation options, and how to configure the geodatabase for efficient data storage and delivery of data access and editing capabilities to many users. Although course exercises use the enterprise geodatabase, many course concepts also apply to workgroup geodatabases. Course goals By the end of this course, you will be able to: * Install ArcSDE technology and configure it for your relational database management system. * Create and connect to a multiuser geodatabase. * Efficiently load and update data in a multiuser geodatabase. * Configure storage settings to support your organization's data management workflows. * Set up user roles and permissions to provide secure data access. * Apply best practices to optimize geodatabase performance. Additional resources ArcGIS Resource Center - http://resources.arcgis.com This site provides unified access to web-based help, online content, and technical support. Esri GIS Dictionary - www.esri.com/gisdictionary This dictionary includes definitions for GIS terms related to geodata, analysis, GIS modeling and web-based GIS, cartography, and Est software. Installing the course data Some exercises in this workbook require data. Depending on the course format, the data is available on a DVD in the back of a printed workbook or as a data download. To install the data, place the DYD in your disc drive or double-click the data download and follow the instructions in the installation wizard. The data will automatically be installed in the CAStudent folder.Disclaimer: Some courses use sample scripts or applications that are supplied either on the DVD or on the Internet. These samples are provided "AS IS," without warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Esri shall not be liable for any damages under any theory of law related to the licensee's use of these samples, even if Esti is advised of the possibility of such damage. Permission to use, copy, and distribute these sample scripts is hereby granted, provided there is no charge or fee for such copies.Icons used in this workbook Notes point out additional information, exceptions, or special circumstances that apply to a particular topic or procedure Tips provide brief help for performing a task or clarifying concepts. External resources provide optional, special-interest information about course topics. Best practices offer industry or professional guidelines, help set goals or priorities, and save time. Estimated times provide guidance on approximately how many minutes an exercise will take to complete. Wernings alert you to potential problems or to actions that should be avoided.Key terms ArcSDE. databases geodatabases Using the geodetabase Using the geodatabase Introduction There are many methods of storing geographic data such as databases, shapefiles, and geodatabases. In this course, you will focus on storing your data in the geodatabase to take advantage of features. available only with a geodatabase, such as distributed data workflows and spatial behaviors. There are several types of geodatabases, so first you will need to choose which type to use. After that, you can implement a worklow for creating a geodatabase, migrating your data, and maintaining the geodatabase Topics covered * Databases and geadatabases * Geodatabase types and licensing * The geodatabase workflow Learning objectives After completing this lesson, you will be able to: * Identify reasons to use the geodatabase. * Compare and contrast single-user and multiuser geodatabases, * Explain the steps of the geodatabase workflow. 1LESSON 1 3 AecGIS Help Library Database subsection in Geodata Table 1.1 Why use a geodatabase? ArcGIS can use spatial data stored in both geodatabases and databases, Database spatial data can be used natively in ArcGIS, and you can even perform a few management tasks through ArcGIS. But geodatabases are stil the recommended way of storing your spatial data. 1. Compare and contrast geodatabases and databases by listing functionality for each in the boxes provided. Geodatabases DatabasesTable 1.2 Desktop format goodatabase descriptions Desktop format geodatabases Using the geodstabase Desktop format geodatabases are typically used for indiv dual purposes where access by multiple users rarely occurs. They can also be used as part of replication scenarios for distributing deta. (ad Functionality | Original Desktop format | Improved Desktop format Storage Microsoft Access File folder; displays gab mechanism | database (.mdb) extension in AicCatalog Storage 2.GB per geodatabase; | 1 TB per object, lirnit effective limit ~500 MB | configurable to 256 TB User limi Jeditorperdatabase —_| 1 editor per object Platform Windows Any Licensing | ArcGIS for Desktop ArcGIS for Desstop You will normally want to choose the file geodatabase over the personal geodatabase for your file-based data format secause of performance, reduced editing constraints, and relaxed size limitations, among other considerations.LESSON Table 1.3 ‘AceSDE technology geodatabase descriptions ArcSDE technology geodatabases AreSDE technology geodatabases provide additional functionality for isolating versions and tracking changes. They are commonly used when many users need to access the same database or when data must be distributed among users across networks Functionality | Distributed | Departmental Large capacity data or project | projects or small | and user base use organizations Storage Microsoft SOL] Microsoft SQL SQL Server, mechanism | Server Express | Server Express Oracle, PostgreSQL, DB2, Informix 10 GB per 10 GB per Limited by database database server | RDBMS and server hardware User limit | 3users,1.can_ | 10 concurrent Unlimited edit users, all can edit Platform Windows Windows Any Licen: ArcGIS for ArcGIS for Server | ArcGIS for Server Desktop Workgroup Enterprise Edition Standard or | Edition Advanced Choosing between the workgroup and enterprise | geodatabases depends heavily on the amount of data bein stored and the number of simultaneous users. 7 |Figure 1.1 “The workflow for setting Up and maintaining a geodatabase, which you will follow throughout the Using the geodatabase Geodatabase workflow Throughout the class, you will follow a workflow for setting up and maintaining a geodatabase. With variations to account for the structure and work pattems of your organization, you can also follow this workflow when you return to work. Maintenance ) Create Creating a geodatabase varies depending on the type of geodatabase you create. For example, when you create a fle geodatabase, a folder with binary files is created in the file system. With an enterprise geodatabase, system tables are added to an RDBMS database. Connect Connecting to a geodatabase allows you to access and potentially manage the data in the geodatabase. You can connect to ‘olders that contain file-based geodatabases, or to database servers for geodatabases stored in an RDBMS. Load data Loading data can be performed as part of several workflows, including setting up your geodatabase for the first time, or updating datasets when new data becomes available as part of maintenance. Either way, data can be loaded as new datasets or as adclitions to existing datasets,Lesson 4 Step 1: Explore data sources You have gathered a few test data sources from different departments to test creating one centralized geodatabase for all the Naperville government departments to use. You will start with exploring these datasets so you can determine how to load them into a geodatabase. @ Open Windows Explorer and navigate to C:\Student\CMGD Database, You will begin with migrating boundary data and the stormwater and sewer network @ Open the AdministrativeArea folder. 1. What data format is used for the datasets in the folder? 2, What datasets are in the folder? @ Retum to the C:\Student\CMGD\Database folder. @ Find the StormwaterSewerNetwork.XML file. 3. What kind of data storage format is used for this dataset? Data can be stored in many different formats, including shapefiles, geodatabases, and XML formats. You may encounter many different formats of data as you begin to migrate to a centralized geodatabase. Geographic data looks very different on the file system than when viewed through ArcGIS. You will now look at the data from ArcMap. @ Open ArcMap. Hint: There may be a shortcut on your desktop or pinned to the taskbar. Ifnot, you can search for ArcMap from the Start menu in Windows 7.Using the geodatabase @ In the ArcMap—Getting Started dialog box, check the box to not show this dialog box in the future and then click OK @ Open and pin the Catalog window to the right side of the ArcMap interface. To view file-based data (shapefiles, file and personal geodatabases, Microsoft Excel files, ete.) you will need to connect to the folder it is stored in, @ In the Catalog window, click Connect to Folder £4 and connect to the CAStudent\CMGD folder. Hint: The C:\Student folder and the Student folder under Desktop are not the same. You can find drive C under Computer. @ In the Catalog window, expand the C:\Student\CMGD\Database\AdministrativeArea folder. 4. How does this view of the boundary data differ from what you saw in Windows Explorer? You will continue to use ArcGIS for Desktop throughout this class to view and manage geographic data sets. Step 2: Create a geodatabase You will now create the file geodatabase that you will be using in this exercise. @ In the Catalog window, create a new file geodatabase named NapervilleTest in the .\CMGD\ Using Geodatabases folder. Hint: Right-click the folder and chose New > File Geodatabase. Creating a new file geodatabase creates a folder in the file system and populates it with a series of binary files that are used for structuring the geodatabase and storing data in it. @ Restore Windows Explorer. @ Navigate to C:\Student\CMGD\UsingGeodatabases. There is a new folder called NapervilleTest.gdb. The gab file name extension identifies tre folder asa file geodatabase.LESSON 1 @ Open the NapenilleTest.gdb folder. You can see a series of binary files that represent tables and indexes. This is the base schema for a file geodatabase, Step 3: Load data into the geodatabase You have two boundary shapefiles and an XML workspace document containing a feature dataset with a geometric network to load. You will start with the shapefiles. @ Return to the Catalog window in ArcMap. © View the properties for the MunicipalBoundary shapefile in the ..\Database\AdministrativeArea folder Hint: Right-click the shapefile and choose Properties. @ View the Fields. The shapefile contains fields for tracking the last editor and date of edit, but the city boundary is not edited, so you will not need these fields. You will create a new feature class with all the fields from the shapefile except those pertaining to edits, and then load the boundary into the new feature class, Create a new polygon feature class in the NapervilleTest geodatabase called Iya g MunicipalBoundary. * Import the coordinate system from the MunicipalBoundary shapefile by clicking the arrow next to Add Coordinate System @ and choosing Import. * Accept the default tolerance, resolution, and keyword. * In the Fields section, choose Import and add the fields from MunicipalBoundary. * Delete the fields related to edit tracking by selecting the fields and pressing DELETE on your keyboard. Hint: Right-click the geodatabase and choose New > Feature Class, and then follow the prompts You can now load the boundary data into the new feature class.Using the geodatabase Use the Simple Data Loader to load the boundary data from the shapefile to the new feature pI Pe class, accepting all defaults Hint: Right-click the feature class and choose Load > Load Data, and then follow the prompts. You will now load the remaining shapefile. @ Use Import Feature Class (single) in the geodatabase to add the CountyBoundary shapefile. * Name the new feature class CountyBoundary, Hint: Right-click the geodatabase and choose Import > Feature Class (single). Lastly, you will import the stormwater and sewer geometric network. The Utilities department has already been taking advantage of the geodatabase to create a geometric network, behavior that is available only in the geodatabase. To provide you with the network for your testing, department staff exported it to an XML workspace document, which allows for storing schema (including geodatabase behavior) and feature data. @ Import the StormwaterSewerNetwork xml file from the Database folder into the geodatabase, accepting all defaults. Hint: Right-click the geodatabase and choose Import > XML Workspace Document, and then follow the prompts. You now have enough data loaded into your file geodatabase to start a few basic tests of functionality with your geodatabase. Step 4: Administer the geodatabase Now that you have a few data sets in your geodatabase, you will test some functionality. To start with, you want to apply permissions to the geodatabase. File geodatabases ate stored in the file system, and permissions are managed there as well @ Restore Windows Explorer and refresh the view of the Naperville Test.gdb folder. I Ps 5. Are there any files that have names that are easily identifiable as the feature classes you loaded? Permissions must be applied at the folder, or geodatabase, level, not at the feature class levelLesson 4 6, How could you apply permissions specifying different groups of people to have access to the stormwater and server network and the administrative areas? Step 5: Use the geodatabase ‘As you were gathering test data, you also requested end user requirements. The Utilities department specified that it has several employees who are responsible for editing the stormwater and sewer network, and these users want to be able to perform these edits concurrently. You will test this using two ArcMap sessions. @ In your existing ArcMap session, open anew blank map [). * Discard any unsaved changes to the current map. @ Expand the SewerStormwater feature dataset and drag the ssPressurizedMain feature class into the map. @ On the Editor toolbar 3, start an editing session. Hint: Select Editor and then choose Start Editing, @ Open another ArcMap session and add the ssLateralLine feature class from the SewerStormwater feature dataset to the map. @ Using the Editor toolbar, start editing again. 7. What happened? The file geodatabase restricts editing to one editor per object. An object is a feature class, table, or feature dataset. Because both the ssPressurizedMain and ssLateralLine feature classes belong to the same feature dataset, they cannot be edited by different editors at the same time, 8, How might you have two editors work on both of these feature classes at the same time? @ Close all open ArcMap sections, disearcling any changesUsing the geodatabase © Close Windows Explorer. Conclusion In this exercise, you tested migrating to a file geodatabase to take advantage of centralized storage. The file geodatabase, however, has several imitations that make it impractical for the Naperville government. You were unable to apply permissions to each individual feature class or to have multiple users editing the same feature classes or feature datasets concurrently. For these reasons, as well as the ability to have versioning and distributed data and performance considerations, you have decided to move to an enterprise geodatabase.LESSON 1 Lesson review 1, Why would you use a geodatabase instead of a database to store your data? 2, What are the limitations of a file geodatabase? 3. If you have about 50 GB of data that needs to be accessed by 20 concurrent editors, which geodatabase type should you use?Using the geodatabese Answers to Lesson 1 questions Why use a geodatabase? (page 1-2) 1. Compare and contrast geodatabases and databases by listing functionality for each in the boxes provided, Geodatabases Databases Stores data Stores data | Multiuser access Multiuser Backup/recovery | access Scalability Backup/ Spatial data recovery Behavior Scalability Topologies Spatial data Geometric Replication networks Network datasets Relationship classes Domains Subtypes Versioning Distributed data Exercise 1: Migrate to the geodatabase (page 1-7) 1. What data format is used for the datasets in the folder? Shapefile 2. What datasets are in the folder? County, Municipal, School, and State boundaries 3. What kind of data storage format is used for this dataset? XML workspace document 1-15LESSON 1 4, How does this view of the boundary data differ from what you saw in Windows Explorer? Each dataset is represented as a single entity. In Windows Explorer there were multiple files for each dataset. 5, Are there any files that have names that are easily identifiable as the feature classes you loaded? No. There may be some lock files named with feature class names, but not table files. 6, How could you apply permissions specifying different groups of people to have access to the stormwater and server network and the administrative areas? Store them in a separate file geodatabase, or migrate to an ArcSDE technology geodatabase. 7. What happened? An error states that there are no editable layers. 8. How might you have two editors work on both of these feature classes at the same time? Migrate to an ArcSDE technology enterprise or workgroup geodatabase.Key terms repository What is ArcSDE? What is ArcSDE? Introduction ArcSDE manages the storing of geographic data in an RDBMS. This allows for many users to simultaneously access the data through the network in a highly scalable way. The components of ArcSDE are a repository of tables and SOL code in the database, a translator to create SOL calls based on client interaction, and managerrent tools. Understanding what ArcSDE is and how it works will help you understand how to manage your multiuser geodatabase. Topics covered * Enterprise geodatabase multi-tier architecture * ArcSDE components * Create Enterprise Geodatabase geoprocessing tool Learning objectives After completing this lesson, you will be able to: * Describe the components of ArcSDE. * Describe the roles of ArcGIS clients, ArcSDE, and the RDBMS in the geodatabase. * Create an enterprise geodatabase using geoprocessing tools. 24LESSON 2 Figure 2.1 The thes tiers involved in an enterprise geodatabase are the ROBMS, AvcSDE, and ArcGIS clients. Noarly all management tasks that you will perform ace accomplished through the ArcGIS ciants and ROBMS ters Multi-tier architecture The enterprise geodatabase relies on several software tiers to function, including the RDBMS, ArcSDE, and ArcObjects. Available Functionality Software Organizational Spatially enabled database Versioning; distributed data Storage; backup; recovery \ RDBMS, RDBMS ‘The RDBMS provides storage management within the geodatabase. This includes storing the data as tables, providing access througt database connections, securing the data based on user accounts and permissions, and providing backup and recovery tools. Supported RDBMSs are DB2, Informix, Oracle, PostgreSQL, and SOL Server. ArcSDE. ArcSDE is a mostly invisible tier between an ArcGIS client and the RDBMS. It helps in the creation of SOL. queries to retrieve features from the database and controls storage of spatial data in the database using a series of metadata tables that aid in versioning and distributed data workflows. Itis possible to create a feature class at the ArcSDE level, bypassing ArcGIS client and the geodatabase, but it is not recommended. ArcGIS clients ArcGIS clients include ArcGIS for Desktop, ArcGIS for Server, and ArcGIS Engine applications, which are all created using ArcObjects components. At the ArcGIS client tier, your spatial data in a databaseWhat is AreSDE? actually becomes a geodatabase capable of advanced behavior, including subtypes, topologies, and geometric networks through another set of metadata tables in the database. ArcGIS also gives you access to most management tasks for administering your geodatabase, often in the form of geoprocessing taols that allow you to create Python scripts to automate maintenance. Identify the appropriate software Each software tier provides different components and functionality to the geodatabase. Understanding the multitier architecture helps you determine which management tool or client software you will use for various tasks. For the following scenarios, choose the appropriate software to use. 1. An end user will be editing data and wants to take advantage of domains that have been applied to various fields. 2. The administrator needs to create a backup of the geodatabase. 3. The administrator needs to create a new feature class in the geodatabase 4. The Utilities department has decided to create a geometric network to represent the sewer systemLESSON 2 Figure 2.2 The three components of AeSDE are the translator, the repository, and management tools ArcSDE commandline tools can be installed, but most have recommended altecnatives in AzcGIS for Doelaop, 24 ArcSDE components ArcGIS clients query the geodatabase using an ArcSDE translator that, interacts with management tables in the RDBMS known as the repository, 3 4s = = Translator The translator converts client requests based on layers, extents, definition queries, and other client controls into SQL queries that interact with features. The translator also contributes to the process of spatially filtering features. Repository The repository is a set of tables and stored procedures in the database that supports the geodatabase. The tables hold metadata that helps control the storage and use of the geodatabase tables. Management tools ArcGIS provides a set of management tools for geodatabases, including ArcCatalog, geoprocessing, and AreSDE command-line ‘tools. Some management is done with the RDBMS tools.Figure 2.3, The hierarchy of users in the database is based on what each user is able to do. What is AreSDE? Administrative users ‘There is a hierarchy of users in the database. When the geodatabase is created, two users are important: the database and geodatabase administrators. The database administrator is the most powerful user in your database, and the geodatabase administrative user is the most powerful user in your geodatabase. Database ‘Admin User (sys, sa, postgres) _| Bata owner Data user ] Database ach ‘The database administrator is always created when you install the RDBMS. You will need access to the database administrator account to perform several tasks, including running the Create Enterprise Geodatabase tool Database administrator responsibilities are as follows: * Create database * Create database users and roles, * Grant database access permissions. * Backup and recovery, * Configure storage in the database Geodatabase administrator The geodatabase administrator is created when you create the geodatabase using the Create Enterprise Geodatabase tool, and is normally named sde. It is the most powerful user in the geodatabase, but it is not powerful enough to perform database administrator functions, The user is generally headless, meaning it is not assigned to one particular person, but the credentials should not be widely shared. 25LESSON 2 3 ‘ArcGIS Help Library: User privileges for _geodatabases in... in Geodata 26 Geodatabase administrator responsibilities are as follows: * Own the repository * Manage the ArcSDE configuration * Configure DBTune. * Perform various maintenance tasks. + Manage the top-lovel version. In SOL Server, the GDB admin can be named sde or it can @] be a dbo user. Refer to ArcGIS Help Library: A comparison of geodatabase owners in SQL Server. In Oracle, the master GDB admin user is named sde, aut additional geodatabases in the same Oracle instance can have other admin user names. Privileges The Create Enterprise Geodatabase tool, while creating the SDE user, also grants it privileges required for creating and administering the geodatabase. Privileges include connecting, creating tables, procedures, views, triggers, and the ability to remove connections from the database,§ ArcGIS Help Library: Creating a geodatabase in in Geodeta Table 2:1 Create Enterprise Geodatabase tool functionality Who is AreSDE? Create and enable enterprise geodatabases ‘The Create Enterprise Geodatabase tool is used to properly set up a database to be used as a geodatabase. This can include creating a database or tablespace and SDE user. It also creates the geodatabase repository. Specific operations performed by the tool depend on the underlying RDBMS. The Enable Enterprise Geodatabase tool car be used to add a geodatabase repository to an existing database. This is especially useful f you want to add geodatabase functionality to an existing database, orif you want to pre-create the sde user as an OS user. Create Enterprise Geodatabase tool requirements Before running the Create Enterprise Geodatabese tool, you must ® Install the RDBMS. ® Install an ArcGIS client. ® Install an RDBMS client. * Have database administrator credentials. t — Function SOL Server | PostgreSQL | Oracle | Creates a databace v Z Creates a tablespace ; ef Creates a GDB admin user R P 2 ZF Grants admin user privileges Vv Wg 17 Crestas a GDB repeatingy V7 v wLESSON 2 Create Enterprise Geodatabase tool use in SOL Server When using the Create Enterprise Geodatabase tool with {| SQL Server, you can optionally create the database and QU) the SDE user withthe proper privileges. Ifthe tool creates the database, it will be 500 MB in size with a 125-MBlog file, both created in the default SQL Server location. Table 2.2 ero Instance SOL Server instance name Enterprise Geodatabase : Database Avalid name for a new database that the tool will tool when used with SOL < create OR the name of an existing database to use. Server ‘Authentication | Ifyou chose operating system authentication you Type must be logged in as a member of the sysadmin fixed server role in SQL Server. | eee SE Nien sn NEE DEMS IF operating system authentication isn't chosen, ‘Administrator | provide the user name and password of the and Password | sysadmin user. Sde Owned | Check this if you want the SDE user to own the Schema geodatabase instead of a DBO user. Geodatabase | If SDE schema is chosen, this field will be SDE. Ifthe Administrator | user does not exist, the user will be created. For and Password | DBO schema, these fields are left blank, ‘Authorization | Use the keycodes file created when authorizing File ArcGIS for Server Enterprise Ss SDE or DBO schema? AveGIS Help Library: A Choosing between SDE and DBO largely depends on security comparison of | considerations, including access to administering the database and gsodatabaze owmersin | where users are stored. SDE schema is easiest with a database user SQL Serverin Geodata named SDE, but if DBO schema is used, any users that map to DBO can perform management tasks. 28Table 2.3 Parameters for the Create Enterprise Geodatabase tool when used with Oracle ArcGIS Help Library Mutiple geodatabase in Oracle in Geoctata What is AreSDE? Create Enterprise Geodatabase tool use in Oracle ‘When using the Create Enterprise Geodatabase tool with Oracle, you can optionally create the tablespace used for the geodatabase and the SDE user with the proper privileges. If the tool creates the tablespace, it will be 400 MB and stored in the default location, With Oracle, if you plan to run SQL statements against the default geometry (ST_Geometry), the library must be copied to the Oracle server and the Oracle extproc must be configured Instance TNS network alias or Oracle Easy Connection string. DBMs The database administrator (sys) user name and. Administrator | password, and Password Geodatabase | SDE and a password for the master geodatabase, or Administrator | an existing user for a user-schema geodatabase. and Password Tablespace | A preconfigured tablespace name to be used, OR a valid tablespace name to be created by the tool, OR blank to create a default tablespace called SDE_TBS. Authorization | Use the keycodes file created when authorizing File ArcGIS for Server Enterprise. Multiple geodatabases in one Oracle instance? ArcGIS also supports user-schema geodatabases to store multiple geodatabases in the same Oracle instance. This configuration starts with an SDE schema that feature classes can be registered with, but additional non-SDE users can be configured to contain a separate set of geodatabase tables to keep track of feature classes and other geodatabase objects, so you can connect to each geodatatase in the Oracle instance and see a different list of feature classes and geodatabase objects.LESSON 2 Table 2.4 Parameters for the Create Enterprise Geodatabase tool when used with PostareSOL 240 Create Enterprise Geodatabase tool use in PostgreSQL ‘When using the Create Enterprise Geodatabase tool with PGS Pesar28L you optionally croate the database and configure it to use a pre-created tablespace, as well as create the SDE user and set up privileges Using PostgreSQL has an additional requirement of copying the ST_Geometry libraries to the PostgreSQL server. The public group role will be granted use on the SDE schema, For higher security, you can revoke use for the public and grant it to a more restrictive group. Password Instance PostgreSQL server name. Database Avalid name for a new database that the tool will create OR the name of an existing database to use. Database Connect as the postgres superuser; the user Administrator and | name defaults to postgres. The geodatabase admin must be called SDE. If Geodatabase Administrator and | the user does not exist, it wll be created. Password Tablespace The name of an existing tablespace to be used, or if left blank the database is created in pg_default Authorization File | Use the keycodes file created when authorizing ArcGIS for Server Enterprise= ArcGIS Help Library: Geodiatabase system tablesin Geodata Table 25 Select AreSDE system table descriptions What is ArcSDE? Explore the repository The repository is a set of system tables that enforce geodetabase behavior, store information about the geodatabase, and keep track of the data stored in the geodatabase. There are two types of system tables: geodatabase tables and AreSDE tables. ArcSDE tables There are more than 24 ArcSDE system tables that store metadata about feature classes, versioning, connections, and locks. Table Use Layers Maintains data about each feature class in the database such as spatial types and spatial reference Table_registry Maintains data about all tables registered in AreSDE, not just feature classes. Layer_stats Stores statistics about feature classes that are used by some geoprocessing tools. Layer_locks Stores information about locks on feature classes. Object locks Stores information about lacks on geodatabase objects. Table_locks Stores information about locks on tables registered with ArcSDE. Process_information | Collects ArcSDE session statistics and information In SQL Server, the ArcSDE system table names are prefixed with SDE.LESSON 2 Geodatabese system table a2 Teble 2.6 descriptions Geodatabase tables The geodatabase tables are used by ArcObjects to store information about geodatabase behavior, such as feature classes that belone to feature datasets. There are far fewer (only six) geodatabase tables than ArcSDE tables. Table Use GDB_ltems Any object in the geodatabase that ‘can be indexed or searched (tables, domains, topologies, etc.) GDB_temTypes Provides information on what type of object each item in the GDB_Items table is GDB_ItemsRelationships Provides information on how geodatabase objects in the GDB_Items relate to each other. GDB_ItemsRelationshipTypes Provides information on the type of relationships between geodatabase objects. GDB ReplicaLog Provides information on every replica import or export operation GDB_Tables_Last_ Modified Validates geodatabase system tables when they are cached by the client application.aoninues & | Figure 24 Creation portion of the ‘geodatabase workflow | What is AreSDE? Exercise 2: Create an enterprise geodatabase In this exercise, you will implement the creation portion of the geodatabase workflow. Maintenance You have decided that an enterprise geodatabase is the best choice for the Naperville government. Your first step in the process is to create an enterprise geodatabase on the database server. In this exercise, you will: * Verify requirements for creating an enterprise geodatabase. * Create an enterprise geodatabase. * View the repository tables.LESSON 2 Step 1: Verify requirements There are several requirements you must meet before you can create an enterprise geodatabase. You will check these before attempting to create your goodatabage. First, you need to know the host name of the database server. @ Open the Command Prompt window and run the hostname tool 1. What is the hostname of your server? The remainder of the requirements you will check pertain to the RDBMS. You must have a database server installed and running, you need administrator credentials, and you need an RDBMS client installed on your ArcGIS client machine. You will start with verifying the RDBMS instance. @ Open SAL Server Configuration Manager. @ Inthe tree view, click SOL Server Services. @ Verify that the SQL Server (MSSOLSERVER) service is running, By | tette service i not running, tell your instructor before moving on. @ Close SQL Server Configuration Manager. You will now verify that you have administrative credentials. @ Open SQL Server Management Studio.What is ArcSDE? @ In the Connect to Server dialog box, verify that the Server name matches the hostrame you recorded earlier. * Set the Authentication type to SOL Server Authentication. * Use the Login and Password combo sa/sa12. You have just signed in using database administrator credentials, but you will check to see whether your Windows user accaunt also has administrator rights. @ In the Object Explorer, expand > Security > Server Roles. @ Right-click the sysadmin role and view its properties. @ Verify that a Student user account is in the Role Members list, @ Close the Properties dialog box. You have now verified the database server. You will normally need to install an RDBMS client on the ArcGIS client machine. But because you will be using the same machine as both server and client in this exercise, you will not need to install it separately Step 2: Create an enterprise geodatabase You are now ready to create an enterprise geodatabase. @ Open ArcCatalog. @ In the Search window, search for and open the Create Enterprise Geodatabase tool.LESSON 2 @ Fillin the parameters provided in the following table: | ems type SOL Server | Instance a | Database Naperville Operating System Authentication | Checked Ste Owned Schema | Checked 7 Geodatabase Administrator sde i Password Authorization File CAProgram Files\ESRI\License'10,1\sysgen\ keycodes @ Run the tool. @ When the tool completes, from the Geoprocessing menu, choose Results @ In the Results window, expand Current Session > Create Enterprise Geodatabase > Messages. 2. Based on what you see in the messages, what did the tool do? Step 3: View the repository You have now created your first enterprise geodatabase. You will use RDBMS tools to investigate it and view the repository tables.Whot is ArcSDE? @ Return to SOL Server Management Studio. @ Inthe Object Explorer, right-click your host name and choose Refresh. @ Expand Databases. You now have a database called Naperville that was created by the Create Enterprise Geodatabase tool. Expand Naperville > Tables. pand Nap The repository tables have been added to the database in the sde schema to create a geodatabase @ Close all open applications. Conclusion In this exercise, you used the Create Enterprise Geodatabase geoprocessing tool to create a geodatabase. It created a new database and a geodatabase administrative user, and it put the system tables in the database, creating a geodatabase.LESSON 2 Lesson review 1. What is the repository in a geodatabase? 2, Which management tools would you use to recover your geodatabase? 3. What role does ArcGIS play in the geodatabase? 4, Ifyou create a database in RDBMS tools with a non-default location and then use the Create Enterprise Geodatabase tool to turn it into a geodatabase, what does the tool do?What is AreSDE? Answers to Lesson 2 questions Identify the appropriate software (page 2-3) 1. An end user will be editing data and wants to take advantage of domains that have been applied to various fields. ArcGIS 2. The administrator needs to create a backup of the geodatabase. RDBMS 3. The administrator needs to create a new feature class in the geodatabase. ArcGIS 4. The Utilities department has decided to create a geometric network to represent the sewer system, ArcGIS Exercise 2: Create an enterprise geodatabase (page 2-13) 1. What is the hostname of your server? Answers will vary. 2, Based on what you see in the messages, what did the tool do? * Checked privileges * Created database * Created administrator user * Validated authorization file * Verified that XML support is enabled * Created repositoryKey terms application server connection AreSDE service connection file direct connection Connecting to the geodatabase Connecting to the geodatabase Introduction Connecting to a geodatabase is required to use and manage the geodatabase. There are two types of connections: application server connections and direct connections. As an administrator, you will need to decide which type of connection your users will want to access your geodatabase. Topics covered * Direct connections * Application server connections * Client and server version compatibility Learning objectives After completing this lesson, you will be able to: + Compare and contrast direct connections and applicetion server connections. * Choose and implement a connection strategy. a4LESSON 3 Figure 3.1 With diract connections, the connects directly to the nt software database server and all ArcSDE processing is performed on the client machine. You can obtain the required RDBMS client software from the Esti Customer Care Postal The AreSDE business logic i ual into all ArcGIS liants, 0 you do not eed to install anything Direct connections Direct connections are the recommended way to connect to your geodatabase from ArcGIS. Database Server ‘RDBMS Cent In direct connections, the ArcGIS client interacts directly with the RDBMS to query the geodatabase without any software in the midalle. This requires two things: RDBMS client software and ArcSDE bus ness logic in the client RDBMS client software RDBMS client software is created by the maker of the RDBMS. It allows a user to connect to a database and execute SOL statements against that database. You will need to install the specific RDBMS client software. ArcGIS will use the client software to make the connection to the geodatabase. ArcSDE business logic The ArcSDE business logic is the portion of ArcSDE that translates client requests into SQL queries. The queries created by the translator interact with the dataset tables and the ArcSDE and geodatabase system tables. When direct connections are used, the ArcSDE business logic is actually built in to the ArcGIS client. This means that the ArcSDE processing occurs on the client side instead of the server, side,Figuro 3.2 With application server connections, the client connects to the database server through an AreSDE application sewer, The ‘AreSDE processing occurs inthe application server, Connecting to the geodetabase Application server connections Application server connections are not the preferred method for connecting to your geodatabase, but may be useful in some situations. In application server connections, the ArcGIS client interac:s with the geodatabase through an ArcSDE service running on either the database server or its own server. The ArcSDE service performs all the ArcSDE business logic for translating client requests into SQL commands. For an application server connection, you will need to install and start the ArcSDE service. How does the ArcSDE application server work? The ArcSDE application server connects client applications with the geodatabase using two processes: giomgr and gsrvr. The giongr process is the ArcSDE service listener. Its job is to listen for client connection requests. You will have one giomgr process for each ArcSDE service. A separate ArcSDE service is required for each geodatabase you want to connect to using an application server connection. When it receives a connection request, it performs some validation based on computer system times and client and application version numbers, and then creates a new gsrvz process for the client. The gsrvr process is dedicated to a single application connection and communicates with the database on the client's behalf, so you will have one gsrvr process for each connected client. The gsrvr Connects to the database using the user name, password, and database supplied by the client in the connection request. The grsrv is where all the ArcSDE business logic is executed. After the giomgr creates a gsrvr process and connects it with the client, the giomgr goes back to listening for new connection requests. aaLESSON 3 Table 3.1 Considerations for chosing boetween direct and application server connections Connection considerations Both direct and application server connections have advantages and disadvantages you will need to consider. Software and Configuration | Network | Processing Traffic Location Direct Install RDBMS client Slightly | On the Connection | software on all ArcGIS increased | client clients machine App Server | Install ArcSDE and configure | Slightly | On the Connection | the app server ona sever | decreased | server machine Choose a connection strategy When you choose which connection type to use, you should consider the software installations and configurations required, processing location, and the implications for network traffic. For the following scenarios, choose the best connection type. 1. The database server is at nearly full CPU capacity. 2. You don't have access to all client machines to install RDBMS software, 3. The client machines have recently been upgraded with new hardware, but the database server is several years old. 4, There will be around 50 simultaneous client connections.Teble 3.2 Parameters for the Database Connections dialog box in ArcCatalog Connecting to the geodetabase Creating direct connections Database connections in ArcGIS for Desktop allow you geodatabases. The connection file is created and stored sy to create direct connections to databases and in your user profile in . AppData\Roaming\ESRN Desktop\ArcCatalog, but you can move the connection file to another folder. The dialog changes based on the RDBMS you choose. Database ‘The RDBMS in which your geodatabase is stored Platform Instance SOL Server: -\, Oracle: :/ PostgreSQL: , * IFnot configured with default settings. Authentication Choose OS or DB authentication. If you chase DB authentication, supply a user name and password. Database The name of the database you want to connect to. Oracle: Not applicable Connecting to a specific geodatabase version The Database Connection dialog box in the Catalog window always connects to the default version. But after creating the connection, you can modify the Geodatabase Connection Properties and choose a transactional or historical version, The Create Database Connection tool allows you to create database and geodatabase connections. It takes the same parameters as the Natahase Connections dialog box, but also lets you specify a version to connect to. 35LESSON 3 Table 3.3 Oracle environment variables Table 3.4 PostgreSOL environment 36 Creating the ArcSDE service and connections Before creating an application server connection, you must install and configure the ArcSDE service. Prerequisites Install the RDBMS client If ArcSDE and the RDBMS are not installed on the same server, you will need to install the RDBMS client on the ArcSDE server. Create an SDE user (Linux and UNIX only) On Linux and UNIX, an ArcSDE administrator account (named sce) must be created in the operating system before installing ArcSDE This account will own all ArcSDE system files and directories. The sde account needs to have several environment variables set to be able to locate program files without specifying absolute paths. SDEHOME Location of the ArcSDE installation ORACLE_HOME | Location of Oracle ORACLE_SID Oracle SID value TNS_ADMIN Location of the tnsnames.ora file PATH $PATH:$SDEHOME/bin:$ORACLE_HOME/bin LD_LIBRARY_PATH | $SDEHOME/lib:/usi/lib:/lib:SORACLE_HOME/ lib TWO_TASK Location of a remote Oracle database. If set, ORACLE_HOME and ORACLE_SID are ignored. SSI EEE SDEHOME, Location of ArcSDE installation PATH $PATH:$SDEHOME/bin LD_LIBRARY_PATH | $LD_LIBRARY_PATH:SSDHOME/ lib: libYou can downlasd the ‘AscSDE installation from the Esri Customer Care Portal Table 3.5 ArcSDE services fle example Table 3.6 Operating system services file example Connecting to the geodetabess Installation ‘The ArcSDE installation installs the application server and the command-line tools. These can be installed on any machine, but running the ArcSDE service requires an ArcGIS for Server license for that machine. When you install ArcSDE, you can choose whether to install the application server, the command-line tools, or both. You only need to install ArcSDE if you want an application server or the command-line tools. Everything else is built in to the core ArcGIS product. Configuration Modify the services files To register the ArcSDE service, you must put the service port number and name in two service files, one for the ‘operating system and one for AreSDE, The default service name is esri_sde and the default port number is. 5151, but both can be modified. ArcSDE services file %A\rcSDE_HOME*%\ete\services.sde + ¥ ESRI ArcSDE service name and port number ? esri_sde 5151/tcp Operating system services file Windows: C\Windows\System32\drivers\ete\services Linux/UNIX: Jetciservices esri_sde 5151/tcp # ArcSDE service a7LESSON 3 Table 3.7 Syntax for the sdeservice create operation 38 Start the application server ‘The ArcSDE Administration Commandssdeservice and sdemon are used to create and/or start and stop the AreSDE service. Create the service (Windows only) In Windows, the ArcSDE service is created as a service. This is a two-step process to create a registry key for the service and set the database the service will work with First you create a registry key for the service using the sdeservice create operation, passing in the ArcSDE admin password, the RDBMS type and instance, and optionally the service name or port number. sdeservice -o create | Run the create operation of the sdeservice command. =p | The password for the sde user in the database “d | The database type (SOLSERVER, ORACLE, POSTGRESQL) and instance | Optional. The name of the service if not esti_sde. This must match the services files entry. : ‘Optional. This removes the dependency ‘on the RDBMS server when ArcSDE and the RDBMS are on different servers, Example with AreSDE and the RDBMS on the same server: sdeservice -o create -p sde -d SQLSERVER -i sde_srve Example with ArcSDE and the RDBMS on different servers: sdeservice -o create -p sde -d SQLSERVER, DBSrvr -i sde_srvcTable 3.8 ‘Adlitional syntax for the sdeservice register operation Table 3.9 Syntax for the edemon start and stop operations Connecting to the goodstabase Then you set the database using the sdeservice register operation, passing in the ArcSDE admin password, the RDBMS type and instance, the registry key (ADMIN_DATABASE) and value to set, and optionally the service name (if the service does not have the default name esri_sde). This /s not applicable for Oracle, sdeservice -o register | Run the register operation of the sdeservice command or The registry key. Use ADMIN_DATABASE to set the database. ~ The registry value for the key, the name of the database Example: sdeservice -o register -p sde -d SQLSERVER -i sde_srve -x ADMIN_DATABASE -v mygdb With SOL Server, f you are using DBO schema you must supply the DBO user name, Use the sdeservice register operation to set the SDE_DBA_USER key. Start the service Starting and stopping the service can be done using the scemon ‘command on both Windows and Linux/UNIX or the Services menu in Windows, sdemon -o start | Run the start operation of the sdemen command, sdemon -o stop | Run the stop operation of the sdemen ‘command, -i | Optional. The name of the service ifnot esri_sde. This must match the services files entry. 39LESSON 3 Table 3.10 Parameters for the Create ‘AveSDE Connection File Connecting The Create ArcSDE Connection File tool is used to create a connection file to connect to your geodatabase through the AreSDE service. The connection file can de distributed. ArcSDE Connection File Location The folder where the .sde file will be stored ‘The name of the connection file, Use the .sde- ArcSDE Connection | extension File Name Server ‘The name of the server on which ArcSDE is instal ed Service ‘The name or port number of the ArcSDE service Database ‘The name of the database to connect to. Not applicable for Oracle. Authentication | If you choose Database authentication, supply a DB user name and password, Othenwise your OS credentials are used. You can choose whether the DB credentials are saved in the connection file. Transactional Version The geodatabase version you want to connect to, You can choose whether the version is saved in the connection fileTable 3.11 Client and geodatabase version compatibility Figure 3.3 Functionality in a 10.1 geodatabase based on client version Connecting to the geodatabose Software version compatibility Version compatibility deals with the questions: "What versions cana client connect to?" and "What can the client do after conrecting?" Connections Aclient can connect to a geodatabase at the same release or earlier, maintaining backward compatibility for at least a few releases. Forward compatibility is available starting at 10.1 Client 9.3 | 10 10.1 Geodatabase | 9.3 | 9.3, 10, 10.1 | 9,3, 10, 10.1 Functionality After connecting to a geodatabase, the functionality availaole depends on the client and geodatabase versions. Forward compatibility Before v10.1, older clients could not connect to a newer geodatabase, but this has also changed with 10.1. 10.1 Geodatabase 10.1 Client Because of changes in system tables implemented at version 10. clients at v10.0 are able to connect to a v10.1 geodatabase. giving forward functionality. In other words, you can upgrade your geodatabase to v10.1 before all clients have upgraded, as long as they are at least at v10. However, the v10.0 clients will not be able to interact with any datasets that use 10.1 behavior.LESSON 3 Figure 3.4 Functionality in 2 10.0 geodatabase based on New geodatabase functionality With geodatabases prior to v10.0, clients could connect to older geodatabases but functionality was limited by the geodatabase. This changes with geodatabases v10.0 or later. A v10.1 client can connect directly to a v10.0 geodatabase and create datasets with v10.1 behavior in it. Clients at v10.0 will see the v10.1 datasets but will not be able to interact with them. This allows you to implement new behavior from v10.1 within your upgraded clients before upgrading your geodatabase, Datasets that can have v10.1 behavior are network datasets, mosaic datasets, parcel fabrics, and feature classes with editor tracking. When should you upgrade? Starting with v10.1, you can mix and match which datasets to upgrade independently of upgrading the geodatabase. For example, you could leave your geodatabase at v10.0, but upgrade your mosaic datasets to take advantage of new functionality with your v10.1 clients. Also, you can upgrade your geodatabase without upgracing all contained datasets. For example, you could upgrade the geodatabase, but keep your parcel fabric at v10.0 until the parcel management team is able to upgrade ArcGIS for Desktop. Reasons to upgrade the geodatabase: * New ST_Geometry SOL functions for Oracle and PostgreSQL New SQL functions for all database implementations Edit the DEFAULT version using versioned views Pre-populated SPATIAL_REFERENCES table using EPSG and ESRI codes for portability Connecting to the geodatabase using a v10.1 application serverConnecting to the geodatabase Modify the connection limit An AreSDE command:-line tool is used to modify the SERVER_CONFIG table in the geodatabase, including the maximum allowed connections. The sdeconfig tool has an operation for modifying SERVER_CON=IG called alter, The default value for the maximum number of connections is 64 Table 3.12 Symaxforsdecontig 00 | sdeconfig -o alter Run the alter operation of the sdeconfig tool Parameter and value. -s AreSDE server host name -i | ArcSDE service name or port number, or direct connection information. In AreSDE Administration Command Reference, see Making connections to the geodatabase for more information on direct connection strings. -D Database name, Not applicable in Oracie. mu AreSDE administrative user -p ArcSDE administrative user password Example with SL Server direct connection: sdeconfig -o alter -v CONNECTION: =i sde:sql server :MYSERVER\ INSTANCE -s MYSERVER\INSTANCE -D myDatabase -u sdé -p sce 0035 minutes Figure 3.5, Irnplementing the connection portion of the _geodatabase workflow Connecting to the geodatabase Exercise 3: Configure connections to a geodatabase In this exercise you will implement the connection portion of the geodatabase workflow. ‘maintenance \, mn Dom | Connections to geodatabases are used to do everything from viewing data to administering the geodatabase. There are two ways to connect to a geodatabase: direct connections and application server connections. You will explore both types of connections before you decide which type you want your users to employ. In this exercise, you will: * Create a direct connection to your geodatabase * Create an application server and use it to connect to your geodatabase * View connections 345LESSON 3 Step 1: Create a direct connection You will start with creating a direct connection, the preferred method for connecting to a geodatabase. The only prerequisite for creating a direct connection is to install the RDBMS client software, which you can download from the Esri Customer Care Portal. But because you are using one machine for both client and server in this exercise, you do not need to install the client software. @ Open ArcCatalog. @ In the Catalog tree, expand Database Connections, @ Open the Add Database Connection tool and fill it in based on the following parameters: Database Platform | SQL Server Instance Authentication Type | Database authentication User Name: sde Password: sde Database: Naperville @ Rename the connection SDE@Naperville. @ Double-click the connection to connect. You have not loaded data into your geodatabase yet, but you can tell that it is connected by right-clicking the connection and seeing many administrative tools available. Step 2: Configure the application server Now you will explore the application server connection.Connecting to the goodatabase Before you can create the connection, you must install and configure the application server, A Do not close ArcCatalog! You will be using it and the direct connection you just created. Open Windows Explorer and navigate to C: \Installers P Pl @ Run ArcSDE_for_Microsoft_ SQL_Server_101.exe. * Save the files to CAnstallers. * After the files extract, keep Launch the setup program checked and click Close. ren the Arc’ 1 for Microsoft SQL Server Setup window opens When the ArcSDE 10.1 for Mi oft SOL, Setup wind yp * Accept the license agreement. * Note on the Select Features panel that both the command-line tools and the application server are being installed. * Accept the rest of the defaults and install Before you can create and run the service, you need to configure a name and port number for the service to run on in services files for the operating system and ArcSDE, @ In Windows Explorer, navigate to C:\Program Files\ArcGIS\ArcSDE\sqlexe\ete. @ Open services. sde in Notepad This file contains a list of ArcSDE services, port numbers, and protocols on an ArcSDE server. @ Uncomment the esri_sde service line by removing the # @ Copy the whole esri_sde service line. @ Save and close the file. @ In Windows Explorer, navigate to C:\Windows \System32\drivers\ete. Open services in Notepad. Ps Pi 7LESSON 3 This file contains a list of service names, port numbers, and protocols that the operating system references, @ Scroll to the bottom of the file. @ Paste in the esri_sde service line you copied from services.sde. @ Add a comment to the line, such as #ArcSDE service. @ Save and close the file. Now you can create and start the service. ©@ Open the Command Prompt window. By | tetne command Prompt was already open from a previous exercise, restart it. @ Type sdeservice and press ENTER. @ View the help for the sdeservice tool. 1. Which operation do you think you should use to make a new service? @ Register a new service with Windows using sdeservice -o create and the following parameters: You do not need to supply a SQL Server instance name because you are creating the application server on the same machine as the database server and you are using the default SQL Server instance. You also do not need to supply an ArcSDE service instance name because you are using the default name and port number.Connecting to the geodatabase You need to update the service configuring the database it will interact with, @ Set the database using sdeservice -o register and the following parameters: -d | SOLSERVER -p | sde -+ | ADMIN_DATABASE ~v | Naperville Now that the service is created and set up, you can start it. You can use the sdemon command-line tool, or in Windows you can use the Services program. @ From the Start menu, search for and open Services. @ Find the ArcSde Service (esri_sde) entry and start the service. @ Open the Task Manager. @ View processes alphabetically and verify that you have a giomgr process. You now have a running application server to connect through Step 3: Connect using an application server You can now connect through your application server to your geodatabase. @ From ArcCatalog, open the Search window. @ Search for and open the Create ArcSDE Connection File tool. 319LESSON 3 @ Run the tool with the following parameters ArcSDE Connection File Location C:AStudent\CMGD\CreatingConnections AreSDE Connection File Name App Server Naperville Server Senice ewido Database : Naperville Database authentication Checked - User name se Password sde —_ the port number instead. @ Inthe Catalog tree, expand Folder Connections > C:\Student\CMGD\ > CreatingConnections. @ Double-click the connection to connect. On client machines you will need to modify the operating system services file to use the ‘ArcSDE service name (such as esri_sde). If you do not modify the services file, you must use @ Right-click the connection and notice that there are administrative tool options. @ In Task Manager, verify that you now also have a gsrvr process. Step 4: View connections Now that you have created two connections, you will view the connection metadata stored in the system tables, ‘@ Open SOL Server Management Studio and connect with Windows Authentication, @ In the Object Explorer, expand Databases > Naperville > Tables. 3.20Connecting to the geodatabace @ Find the SDE_process_information table. @ Right-click the table and chose Select Top 1000 Rows. 2, How many connections are recorded in the table? @ Scroll until you can find the connected user (owner), connection type (direct_connect), and client host (nodename) fields, 3. Record the information for the connections. @ Close SOL Server Management Studio. @ In ArcCatalog, right-click your direct connection and choose Administration > Administer Geodatabase. @ View the Connections tab. 4, Do the connections reported in ArcCatalog match those you saw in the system table? ‘One of the administrative tools introduced at ArcGIS 10.1 is the ability to view and marage connections to your ArcSDE geodatabase through ArcGIS, Step 5: Choose a connection strategy You have now set up a direct connection and an application server connection, and have found that the application server connection will result in many processes running on your database server, consuming processing power. You have conducted some surveys and found that you will have at least 50 concurrent users connected to the geodatabase at any given time.LESSON 3 5, Do you think Naperville should use application server connections or direct connections? Close AreCatalag and the Command Prompt window. g p @ From Services, stop the ArcSDE service. @ Close any other open applications. Conclusion In this exercise, you created a direct connection, configured an application server, created an application server connection, and viewed connections. After exploring both connection types, you determined that a direct connection strategy will work best for Naperville.Connecting to the geodatabace Lesson review 1. Where does the processing occur in a direct connection? An application server connection? 2. What are the installation requirements for direct connections? 3. Why might you use an application server connection? 223LESSON 3 Answers to Lesson 3 questions Choose a connection strategy (page 3-4) 1, The database server is at nearly full CPU capacity Direct connection 2. You don't have access to all client machines to install RDBMS software. Application server connection 3, The client machines have recently been upgraded with new hardware, but the database server is several years old. Direct connection 4, There will be around 50 simultaneous client connections. Direct connection Exercise 3: Configure connections to a geodatabase (page 3-15) 1. Which operation do you think you should use to make a new service? sdeservice -o create 2. How many connections are recorded in the table? Two 3, Record the information for the connections. SDE | Direct connection | SDE | App Server connection | 4, Do the connections reported in ArcCatalog match those you saw in the system table? Yes 5. Do you think Naperville should use application server connections or direct connections? Direct connections 224Key terms automation environment settings ModelBuilder Loading data into the geodetabose Loading data into the geodatabase Introduction Loading data into your geodatabase can be a lengthy and complex process with multiple ways of doing so. The first step is to determine which tools to use and what settings to apply to improve the performance of your data loads. Topics covered * Data owner user account * Geoprocessing environment settings * RDBMS settings * Data-loading tools and workflows * Automation Learning objectives After completing this lesson, you will be able to: * Explain the importance of the data owner account. * Identify settings that help with data loading. * Implement workflows to load and update data in the geodatabase,LESSON 4 Figure 4.1 The data owner account is more powerful than a data user, but less powerful than either administrative 42 Data owner account The user account that is used to load data in the geodatabase is called the data owner. The data owner is responsible for a variety of management tasks for the data and is therefore a very important user. Database ‘Admin user (sys, 52, postgres) Geodatabase Admin user (sde} Data owner Data owner responsibilities: * Manage permissions Manage fields * Manage indexes © Register data as versioned Because the data owner is responsible for several important maintenance tasks, it is best to create a headless user account (one not assigned to a particular person) to serve as the data owner. This allows you to have several people capable of performing management tasks, You can also pass credentials from person to person as staffing issues require. For example, if John Smith owns the data, only he will be able to manage it. If John leaves his position, no one will be able to maintain the data. But if the data is loaded by a headless account, when John leaves he can pass the credentials to the new data manager. SQL Server has the option of using only OS authentication, which can make a headless account impractical, Alternatively, you could map an OS user logon to a database user in SOL Server. This allows you to log on with OS credentials but keep your data owned by 2a headless entity. Then if the person responsible for deta ownership changes, you can alter the mapping.Table 4.1 Parameters for the Croate Database User tool Loading data into the geodatabese Create the data owner account ‘The Create Database User tool can be used to create users in your database without using RDBMS tools. To create users, you will need to use a connection to the database using database administrator credertials, Input database workspace Create OS Authenticated | Use to add an OS user to the database, The OS Select a connection file for the database you want to create a user in. The connection needs to use database administrator credentials. SQL Server and Oracle only. User user must already exist: Database User name and password for the user, either new to User and be created or existing to be added to the database. Password Fusing an OS user, a password is not required. Role ‘Optionally, the database role to add the user to. Tablespace | Oracle only. Name The default tablespace for the user, new or existing, If blank, the Oracle default tablespace will be used, 43LESSON 4 44 The tool also gives the user specific privileges. © Create table * Create view * Create procedure + View definition * Create session * Create view * Create sequence © Create table * Create trigger * Select on DBA Role * Usage on sde schema “| * Access to publie.geometry_columns and PGS) public spatal_rf-systable if PostGIS is installedTable 4.2 Common data-loading environment settings Leading data into the geodatebese Geoprocessing environment settings Geoprocessing environment settings are parameters that affect a tool's result. They are useful when loading data because rrany times geoprocessing tools are used. They can be set at the application, model, or tool level Transformations Setting Purpose Current Workspace from which inputs are taken and Workspace outputs are placed when tools run Output Output will be reprojected to the specified Coordinate coordinate system System Geographic If the output is reprojected to a different geographic coordinate system, this geographic transformation is used Output CONFIG Keyword The keyword used when creating a dataset ina geodstabase used to specify storage parametersLESSON 4 46 Table 4.3 RDBMS considerations when loading data RDBMS considerations Because you are loading data into a database, RDBMS considerations can greatly affect your data-loading operation. Consideration | Purpose Space Ensure there is enough space in the database for the new datasets Memory Ensure there is enough RAM available for the database to process the data load operation Connections | Time large loads for when there will be minimal connections to the database Logging Disabling transaction logging can speed up the data-loading operationLoading data into the geodatabase Choosing a data-loading tool There are a variety of tools you can use to load data into your geodatabase. The appropriate tool depends on several factors | 1. Fillin the table with information about the date-loading tools. Conversion | Simple Data | Object Leader | Append Tools Loader Description | Converts Loads data Tests behavior | Loads more datasets into an existing | while loading | data into an between dataset using | data into existing formats using | the load complex dataset using a import and option in datasets GP tool ‘export options} ArcCatalog Best Use Case Limitations ‘Automation? Table 4 Datadonding tool propertios 4LESSON 4 48 Figure 4.2 Workflow for updating datasets Updating datasets Sometimes, rather than loading new datasets into your geodatabase, you will need to replace the data within existing datasets with updated data. For example, periodically FEMA re-evaluates to determine flood zones. When FEMA releases new flood zones, counties will want to replace their current flood zone dataset contents with the new flood zones. Updating datasets is a two-step process. First, you delete the existing data using the Truncate Table tool, Then you load the new data into the dataset using the Simple Data Loader, Object Loader, or Append tools The Truncate Table tool removes all rows from a database table or feature class using truncate procedures in the database. Because it does not use database transactions, the removed rows cannot be recovered, but the operation will be faster than row-by-row deletion ‘The Truncate Table tool takes a single parameter, the input table ‘The Truncate Table tool must be run by the owner of the data The Truncate Table tool does not support complex or versioned data. 1, Why would you update a dataset rather than deleting it and creating a new one?Figure 4.3 Individual to executions Figure 4.4 Batch mode execution Figure 4.5 Model execution Loading data into the geodatabase Automation Automation is the process of repeating a workflow, with each iteration potentially using a different set of parameters, Automation can be used to simplify a complex workflow into a single tool, or to repetitively apply the same tool to many datasets. Automation can help make data loading an easier process. An automation scenario Often, when you are creating an ArcSDE geodatabase, multiple feature classes need to be loaded into it. The original feature classes might be shapefiles stored in a folder in the file system or might be from a file geodatabase. You could convert each shapefile individually using a data conversion tool Or you could use the batch mode execution of the tool, This allows you to run the tool once, but you would need to set up all input and output parameters initially Automation can make this process much simpler while creating a tool that can be used over and over on many folders or shapefiles. You could create a model or Python script that iterates through all feature classes in a folder and converts them for storage in the geodatabase. a>LESSON 4 = ArcGIS Help library Executing t Matador aed Creating tools with ModelBuilderin Geoprocessing Figure 4.6 ‘A model for bulk loading multiple feature lasses 410 Using ModelBuilder ModelBuilder allows to you create models—workflows that chain together tools and accept user input for parameters. Models can be used just as geoprocessing tools are used, from ArcGIS applications, Python scripts, and other models. ModelBuilder is graphical in nature. You can easily create, edit, and manage your workflows without, writing code. Creating models Models must be created inside a custom toolbox. You can do this by right-clicking the toolbox and choosing to create a new model, or by creating a new model in ModelBuilder and saving it to a custom toolbox. Toolboxes can be stored in a file system folder or a geodatabase. Model elements. Tools Tools include geoprocessing system tools, Python scripts, and model tools that form the basic building blocks of model workflows. Tools take input variables and create output. Tools can be added using the Add Data tool or the Insert menu, or by dragging the tool from the Catalog, Search, or Toolbox window onto the model canvas. Tools are represented with yellow rounded rectangles. Variables Variables are either inputs or outputs of a tool. There are two kinds of variables: data variables and value variables. Data variables reference data stored on disk; value variables hold values such as strings, numbers, linear units, or spatial references. Variables can be addedLoading data into the geodatabase using the Add Data tool or the Insert menu, or by dragging onto the canvas or creating variables based on tool inputs, Variables are represented using ovals in different shades of blue and green based on whether they are data or value variables and input or output of a tool, It is important to note that output variables from a tool are often reused as input for another tool. iterators Iterators in Mode!Builder allow for looping, or repeating a process over and over. Iterators are used to run the same tool or process many times with different settings or data each time, Iterators are represented with orange hexagons and can be added from the Insert menu, Parameters Model parameters are model variables that have been marked for User input. Model parameters can be specified in the model tool dialog box when the user runs the tool. Variables that are also parameters have a P hovering outside the upper-right of the variable. Variables are marked as parameters by choosing Model Parameter from the variable context menu. They can also be renamed to specify the label used in the model tool dialog box. Running models Models can be run from the Mode[Builder window or by running the model from the Catalog, Search, or Toolbox window like any other tool,Loading data into the geodetabese 30 minutes xX Exercise 4: Load data into the geodatabase In this exercise you will implement the data-leading portion of the geodatabase workflow. Figure 4.7 This exercise focuses on | == loading data into the Maintenance geodatabase. Now that you have a geodatabase created and you have datermined how to connect to it, you will load data into it. Multiple tools are available for loading data into your database, and there are several important ideas to consider as you load your data. You will explore the tools, users, and settings involved in data loading, In this exercise, you wil | * Create a data owner account * Load new datasets into the geodatabase * Update datasets using a model 413LESSON 4 Step 1: Create the data owner account The user who owns datasets in the geodatabase has many management responsibilities. To make sure those maniageriwit lasks cat still be performed even if staffing changes, you will ereate a headless user account to own all GIS data @ Open ArcCatalog, @ Create a new connection to the Naperville database using OS authentication and name it admin@Naperville 1, What level of access will you have by connecting using your OS credentials? 2. Why are you connecting using OS credentials? @ Connect to the database using the new connection. e In the Search window, search for the Create Database User tool @ Run the tool using the following parameters: Input database workspace | admin@Napenille Database User gisowner Database User Password | gisowner @ Open SOL Server Management Studio and log on using Windows Authentication, @ In the Object Explorer, expand Security > Logins. @ Note that gisowner has been created as a server login. a4Leading data into the geodatabase @ In the Object Explorer, expand Databases > Napenille > Security > Users. @ Note that gisowner has been created as a user in the database. @ Close SAL Server Management Studio. @ In ArcCatalog, create a new connection to the Naperville database using the gisowrer credentials and name it gisowner@Naperville You will use this connection to perform all of your data loading, Step 2: Load new datasets You will load a number of datasets into your geodatabase using several different tools. In the Catalog tree, expand Folder Connections > C:\Student\CMGD > Database > 9 LandUsePlanning, There are a variety of planning-related feature classes you will load into the geodatabase @ Using Conversion tools, add FEMAFloodZone, LandUseCurrent, and ZoningDistrict to the Naperville geodatabase. * Make sure to use the gisowner@Napenville connection. * Accept all defaults when migrating the data. @ Refresh and expand the gisowner@Naperville connection and confirm that the datasets have been created in the geodatabase and that they are owned by gisowner, There are two feature classes for planned land use, each created by different GIS technicians. One is for the northern area of Naperville and the other is for the southern area. You will combine both into one feature class called LandUsePlanned in the geodatabase. 3, How might you accomplish this task? @ Create a new polygon feature class called LandUsePlanned in the Naperville geodatabase. * Import the coordinate system and field structure from one of the LandUsePlanned shapefiles. asLESSON 4 @ Use the Append (Data Management) tool to load the data from both LandUsePlanned shapefiles into the new feature class in the geodatabase, You will also load the sewer and storm water network into the geodatabase. @ Import the StormwaterSewerNetwork XML Workspace document stored in the Database folder into the geodatabase using conversion tools. @ View the SewerStormwater feature dataset in the geodatabase. 4, Ifyou had to load more features in to the ssLateralLine feature class and want to be sure that the new features properly connect to existing features, what tool would you use? Step 3: Update datasets Occasionally you will receive new versions of datasets from outside sources, such as new flood zones from FEMA. When you receive these, you need to replace the contents of the existing datasets with the new data. You will do this by truncating the table and then appending the new records into it. You will do this often enough that you have decided to create a model to automate the process. Because you have several staff members who may do the updating, you've decided to store the toolbox containing the tool in the geodatabase for easy access. @ Create a new toolbox named DataLoadingTools in the Naperville geodatabase. ‘+ Make sure you are still using the gisowner@Napenville connection. @ Right-click the toolbox and create a new model @ From the Model menu, choose Model Properties. * Name the model UpdateDataset. * Label the model Update Dataset @ Close the model properties. You will search for and add the required tools to the model. 416Leading data into the geodatabase @ Search for the Truncate Table tool. @ Drag it onto the model canvas. @ Use the same process to add the Append tool @ Use the Connect tool ¢# to connect the Output Table output variable from the Truncate Table tool to the Append tool. * Make sure to connect it to the Append tool's Target Dataset parameter. You will need to provide the model with information about which dataset is being truncated and which dataset holds the new records. @ Choose the Select tool ie @ Right click the Truncate Table tool and choose Make Variable > From Parameter > Input table. @ Right-click the Input Table variable and choose Model Parameter. @ Right-click the Input Table variable and rename it Target Dataset, @ Repeat the process to create a model parameter for the Append tool's Input Datasets parameter. * Name it Input Features Lastly, you need to make a small adjustment to an Append tool parameter. Because you are loading from a shapefile, the schema of the input features will be slightly different from that of the target dataset, The Append tool has the option of enforcing a rule that schema must match, which is enabled by default. You will choose not to test the schemas to ensure they are identical @ Double-click the Append tool to open it. @ Set the Schema Type parameter to NO_TEST and click OK to close the tool @ Save and close the model @ Preview the FEMAFloodZone feature class from the Naperville geodatabase.LESSON 4 @ From the Catalog tree, run the model using the following parameters: | Target Dataset | FEMAFloodZone from the Naperville geodatabase Input ress | FEMAFloodZoncUpdated from the \Database\LandUsePlanning folder @ Preview the FEMAFloodZone feature class again. 5. Is there a change? @ Close ArcCatalog, Conclusion In this exercise, you created a user account that will own all GIS data in the database that is not assigned to a person so that the management of your data can continue after staffing changes. You then began the process of loading data into the geodatabase using a variety of data-loading tools and automation 418Loading data into the geodatabese Lesson review 1, Why might you use the Append tool instead of the Simple Data Loader? 2. Why should the data owner account be a headless user? 3. Why is the Truncate Table tool the fastest way to empty an existing feature class?LESSON 4 Answers to Lesson 4 questions Choosing a data-loading tool (page 4-7) 1. Fill in the table with information about the data-loading tools. Conversion | Simple Data | Object Loader | Append Tools Loader Description | Converts Loads data —_| Tests behavior | Loads more datasets into an while loading | data into an between existing data into existing formats using | dataset using | complex dataset using import and | the load datasets a GP tool export option in options ArcCatalog Best Use Converting | Quickly Loading data | Loading data Case formats loading data | into complex | into existing without into simple | datasets datasets with combining datasets automation datasets Limitations | Each input No complex | Must be done becomes a datasets, from ArcMap separate in an edit feature class output session to load into Automation? | Yes No No Yes Dateloading toal propertios, Updating datasets (page 4-8) 1. Why would you update a dataset rather than deleting it and creating a new one? A lot of functionality is defined based on the dataset, such as geodatabase behavior and permissions that would have to be re-created and applied to the new dataset.Loading data into the geodatabase Exercise 4: Load data into the geodatabase (page 4-13) 1, What level of access will you have by connecting using your OS credentials? Database administrator 2. Why ate you connecting using OS credentials? Database administrator access is required to create user accounts. 3. How might you accomplish this task? Create a new feature class and use the Simple Data Loader to load both feature classes data into LandUsePlanned. 4. Ifyou had to load more features in to the ssLateralLine feature class and want to be sure that the new features properly connect to existing features, what tool would you use? Object Loader 5. Is there a change? Yes, there's a large triangular flood zone in northwest Naperville. 421Key terms DBTUNE keyword parameter Managing storage Managing storage Introduction When loading data into a database, you can set several parameters to affect the way the data is stored. These parameters are grouped into keywords that are selected when creating new datasets in the geodatabase Topics covered * Configuration keywords * DBTUNE Learning objectives ‘After completing this lesson, you will be able to * Describe the purpose of configuration keywords. * Use command-line tools to modify DBTUNE.LESSON 5 Figure 5.1 Questions ta atk yourself when considering how to store geodatabase data 7 ArcGIS Help library DBTUNE configuration parametorsin your RDBMS section 52 Configuration parameters Configuration parameters and values specify how tables, indexes, data, and other objects are stored in the database. Where should a table or Index be created? Whot spatial format should be | - ued? character data be eset How full should Index pages be? 3 \ y When ArcGIS creates objects in the geodatabase, it must tell the database how to store those objects, whether they are tables, indexes, or even raster or text attributes, as well as spatial data ArcGIS does this using configuration parameters. You can customize storage by setting configuration parameters ete \ Configuration parameters can control where to create a table or index (which Oracle or PostgreSQL tablespace or SQL Server file group), how densely to pack indexes, whether to use unicode character encoding, and which spatial type to use to store features. Alarge number of configuration parameters are available, but they do vary based on RDBMS.Figure 5.2 The DEFAULTS keyword contains default values for all cantiguration parameters Figure 5.3 Geography keyword in SOL Server Managing storage Configuration keywords Configuration parameters are grouped into configuration keywords. Instead of specifying every single parameter individually, a user only needs to pick a keyword that refers to a whole grouping of parameters. DEFAULTS ArcGIS gives you several keywords out of the box, including the DEFAULTS keyword. The DEFAULTS keyword gives you default values for all configuration parameters for your RDBMS, The DEFAULTS. keyword is the default keyword used by ArcGIS when creating datasets in the geodatabase. aN Geography GEOMETRY _STORAGE ArcGIS also provides additional named keywurds out of the box for common nondefault configurations. For example, in SQL Server, there is a keyword for using the geography spatial type rather than the default geometry type. Named keywords typically have only a fewLESSON 5. Figure 5.4 od keyword for not using unicode | Auserconfig character encading 54 configuration parameters set—only those that have different values from what DEFAULTS has. For all parameters that are not specified in a named keyword, ArcGIS will use the values from DEFAULTS, No_Unicode You can also create your own keywords for any configuration you want. An example of this would be to create a keyword that specifies not using unicode character encoding. End users can choose out-of-the-box keywords like DEFAULTS ora custom keyword when creating datasets.Table 5.1 ‘A subset of a D8TUNE table DBTUNE Managing storage DBTUNE is a table in the geodatabase repository that stores configuration keywords and parameters. Each keyword has one or more records in the table associated with it for each configuration parameter in that keyword. keyword parameter name config_string DEFAULTS — | B_INDEX_ROWID WITH FILLFACTOR = 75 DEFAULTS | GEOMETRY_STORAGE | GEOMETRY DEFAULTS | UNICODE_STRING TRUE : GEOGRAPHY | GEOMETRY_STORAGE | GEOGRAPHY GEOGRAPHY | ULTEXT Geography READ_ONLY | B_INDEX_ROWID WITH FILLFACTOR = 100 READ_ONLY | ULTEXT Read Only Data When ArcGIS creates datasets, it retrieves all parameters for the specified keyword (and additional ones from DEFAULTS if the named keyword doesn't specify them) and uses those to create the dataset in the RDBMS.LESSON 5. 56 Figure 5.5 Workflow for updating DBTUNE Create and update keywords An ArcSDE command-line tool is used to modify the DBTUNE table in the yeodatabase, The sdeubLune tool has several operations for modifying DBTUNE including alter, delete_data, and insert to directly modify the table. You can also export the table to a text file, modify that, and reimport it using the export and import operations. ‘There are several reasons you might want to modify DBTUNE. You might want to modify the DEFAULTS keyword to use your preferred configuration without requiring your end users to select @ keyword every time they create datasets. This is the best practice for configurations that should be used most or all of the time. For example, if you always want to use the geography spatial type rather than geometry in SQL Server, you should modify the DEFAULTS. keyword to use geography. You might also want to create a custom keyword that users can choose some of the time. This is best if the configuration is used occasionally, but should not be considered the default. As an example, you may want to store read-only data with more tightly packed indexes because the data and indexes won't be changing Editing DBTUNE Exporting, editing, and importing your DBTUNE table is the easiest way to see what the configuration looks like, and visualize the changes you are making to it. Expr OSTUNETable 5.2 Table 5.2 New keyword in OBTUNE | example Managing storage Step 1: Export DBTUNE First, you export the DBTUNE table to a text file to be able to easily edit it. sdedbtune -0 export Run the export operation of the sdedbtune tool. -f DBTUNE file name and path -s AreSDE server host name -i | ArcSDE service name or port number, or direct conrection information In AreSDE Administration Command Reference, see ‘Making connections to the _geodatabase for more information on direct connection strings, -D Database name, Not applicable in Oracle ~u ArcSDE administrative user =p ArcSDE administrative user password Example with SQL Server direct connection: sdedbtune -o export -£ dbtune.txt vi sde:sqlserver: SOLSERVERINSTANCE, -D myDatabase -u sde -p sde Step 2: Edit in text editor Use a text editor to modify or create a keyword. ##NO_UNICODE UNICODE_STRING "FALSE" Urtext" END saLESSON 5. If the ULTEXT parameter is not set, the keyword will not appear in the ArcGIS interface, Step 3: import DBTUNE After altering or creating a keyword in the OBTUNE file, you need to import the file to modify the DBTUNE table in the geodatabase. This is done using the sdedbtune -o import operation with the same parameters used for exporting DBTUNE. Example with SOL Server direct connection: sdedbtune -o import -f dbtune.txt si sde:sqlserver: SOLSERVERINSTANCE, -D myDatabase -u sde -p sde Step 4: Use keywords Now that you have created the keyword, end users will be able to choose it from a drop-down list whenever a configuration keyword is a parameter for a tool in ArcGISManaging storage 25 minutes x Exercise 5: Customize storage using configuration | keywords In this exercise you will customize the data-loading portion of the geodatabase workflow. Figure 5.6 Customizing storage ‘options when loading data Maintenance You have decided to store read-only data with tightly packed indexes to avoid fragmentation. To do this, you will create a new configuration keyword in DBTUNE that your end users can use when loading read-only data. In this exercise, you will: * Create a configuration keyword. * Use your new configuration keyword to load data. 59LESSON 5: Step 1: investigate Help documentation Because configuration parameters control the storage of objects in a database, they are specific to the ROBMS. You can view a list of supported parameters for each RDBMS in the ArcGIS Help Library. @ From the Start menu, search for and open ArcGIS 10.1 for Desktop Help. @ In the tree view, expand Geodata > Administering geodatabases. There are sections for each RDBMS supported for use as a geodatabase. @ Expand Geodatabase in for your chosen RDBMS. @ Expand Setting up a geodatabase in > Advanced Configuration > DBTUNE in . @ View DBTUNE configuration parameters, You will want to return to this page later when you decide whether you will be modifying or creating keywords. This page will help you determine which parameters you can modify and what possible values you can put in them @ Close your browser. Step 2: Export DBTUNE To create a configuration keyword, you will start by exporting the existing DBTUNE table to a text file where you will be able to view and edit it. @ Open a command prompt. @ Change directories to C:\Student\CMGD\DBTUNE by typing ed C:\Student\CMGD\DBTUNE.Managing storage @ Use the sdedbtune command-line tool to export a copy of DBTUNE using the following arguments: -o | export +f | dbtune.txt i_| sde:sqlserver: -D | Naperville su | sde -p | sde @ In Windows Explorer, navigate to C:\Student\CMGD\DBTUNE. Open dbtune.txt with Notepad, Pp Pe @ Look through the file. 1, What appears at the top and bottom of each keyword? 2. How are parameters and values formatted? Step 3: Edit the file @ Scroll to the bottom of the file. @ Add the start and end lines for a new keyword called READ_ONLY. @ Return to Windows Explorer and open read_only.txt in NotepadLESSON 5 To tightly pack indexes for read-only data, you will set all index parameters for the business tables to use a fill factor of 100. This means that index pages will be filled 100 percent without leaving room for growth. This is good for read-only data because the indexes won't be changing, This will work in SQL Server and PostgreSQL, In Oracle, a similar concept exists, but itis called PCTFREE (percent free). To fully pack the indexes you would want a percent free of zero. © Copy the entire contents of read_only.txt and paste it between the start and end lines of the new keyword in dbtune.txt. @ Save and close dbtune.txt. @ Close read_only.tt. Step 4: Import DBTUNE @ Retum to the command prompt. @ Use the sdedbtune -o import operation with the same arguments as the sdedbtune -o export ‘operation to import the new dbtune information. * Type Y and press ENTER when asked if you are sure. Hint: In the command prompt, you can press the up arrow to recall the last operation, edit it, and then run the modified command. You have created a new keyword that your end users will be able to use to load data into the geodatabase. @ Close the command prompt. Step 5: Use the keyword to load data @ Open ArcCatalog. @ In the Catalog Tree window, expand Folder Connections > C:\Student\CMGD > Database > Administrative Area 52Managing storage @ Export CountyBoundary.shp to the geodatabase: * Use the yisowrer @Naperville connection as the Output Location. * Call the feature class CountyBoundary. * In the Feature Class to Feature Class tool, scroll to the bottom and expand Geodatabase Settings (optional). * Choose the READ_ONLY keyword. @ Repeat the process to load MunicipalBoundary.shp into the geodatabase. @ Close all open applications Conclusion You have created and used a keyword that customizes the storage of feature classes in your geodatabase. In this exercise, you tightly packed indexes for read-only datasets, but there are many other ways you can customize storage using configuration parameters and DBTUNE.LESSON 5 Lesson review 1, What are configuration parameters? 2, What are configuration keywords? 3. What are the three steps for creating a new keyword in DBTUNE?Managing storage Answers to Lesson 5 questions Exercise 5: Customize storage using configuration keywords (page 5-9) 1, What appears at the top and bottom of each keyword? ##KEYWORD_NAME END 2. How are parameters and values formatted? Each parameter has its own line, and the value is separated from the parameter name using tabs.Key terms ArcSDE compressed binary spatial field types Spatial pes Spatial types Introdu nm The format in which geographic data is stored is called its spatial type. In most RDBMSs, you have a choice of two or more different spatial types for storing your geographic information, At some point, you may need to configure a dataset to use a nondefault spatial type, or to convert between spatial types Topics covered © Spatial types * Configuring spatial types * Converting spatial types Learning objectives After completing this lesson, you will be able to: * Define spatial types. * Choose and configure spatial types. * Migrate from one spatial type to another. 61LESSON 6 Figure 6.1 SDE binary data uses base, feature, and spatial index tables to store data, Figure 6.2 Spatial field types store ‘geographic information in line in the business table, 62 ArcSDE compressed binary ArcSDE compressed binary is one method of storing spatial data in a geodatabase using Oracle or SQL Server, but itis no longer the default method of storing data. _ x u Res Zoning F nt fees nn 5 Polygen Fig Ses iE See 2 s19 SDE binary uses three tables to store a feature class. The first is ¢ business table that holds attribute information and an ID number for linking to the spatial data, Second, the feature table holds the geometry of the feature. Finally, a spatial index table holds information for quickly retrieving features. But the multiple tables used with SDE binary make access of feature information through SQL code and third-party applications more difficult, Spatial field types There are many spatial field types supported in geodatabases, including Esri's ST_Geometry and SQL Server's Geometry types. a 1 Ox00002A1 Res Zoning Spatial field types store geographic information in the business table with the attributes, This allows for access to the data through SOL code. The default spatial types in all RDBMS are spatial ficld types.Tablo 6.1 Supported spatial types in SQL Server, Oracle, and PostgreSQL requirements Spatial types Supported spatial types Supported spatial types differ by RDBMS, including which spatial type is the default {sau} [ona Esri ST_Geometry we we Esri SDE Binary ff af SAL ServerGeomety | 25 SOL Server Geography | 7 Oracle Spatial 2 Esri ST_Geometry Esri's ST_Geometry is a user-defined data type that allows for defining columns that store spatial data in your business tables. ST_Geometry is the default spatial type for Oracle and PostgreSQL geodatabases. Esri SDE Binary Esri's ArcSDE compressed binary storage type uses a binary mechanism for storing geometry. The geometry is compressed by the client and passed to the database for storage. This means that the client must know how to compress and uncompress the geometry SDE Binary also uses multiple tables to store the feature class information, including the business table for attributes, the feature table for geometry, and a spatial index table. The client must be aware of all these tables. SDE Binray is an older format that was used extensively in SQL Server and Oracle, but it is no longer the default in any RDBMS. SDE Binary is still a great choice for storing features that have many vertexes, such as coastline data. 63LESSON 6 ba SQL Server Geometry SQL Server Geometry is similar to existing GIS spatial types in that it stores coordinates in an arbitrary plane, allowing for both geographic and projected coordinate systems. The geometry is stored in a column in the business table. SOL Server comes standard with two spatial types, sa na additional installation is necessary. This is the default spatial type for geodatabases in SOL Server. SQL Server Geography SOL Server Geography is similar to SQL Server Geometry, but it can only store coordinates in geographic coordinate systems using latitude and longitude. Using the Geography type gives you access to SOL functions that calculate distance and area on a curved surface. Oracle Spatial Oracle Spatial is an optional feature of the Oracle Database Enterprise Edition that uses the SDO_Geometry type to store geographic information as a column in the business table. The SDO_Geometry type can also be used with Oracle Locator, which is a standard feature of Oracle Database Standard and Enterprise ecitions and a subset of Oracle Spatial. In addition to the SDO_Geometry type, Oracle Spatial and Oracle Locator provide geospatial capabilities and a SQL API. ArcGIS is capable of reading and creating feature classes that use SDO_Geometry for their storage mechanism PostGIS Geometry PostGIS adds a spatial type to PostgreSQL using OGC well-known text or binary specifications for representing geometry. ArcGIS supports the Geometry type, but not the Geography type. Geometry is stored in a column in the business table. PostGlS is an adgitional installation you must perform after installing PostgreSQL, which creates a PostGIS template database that you must use to create a database to use as your geodatabase. Using PostGIS will require you to manually create your database, sde user, and schema, and then use the Enable Enterprise Geodatabase geoprocessing tool to create the repositoryTable 6.2 Sb Spatial types Configuring spatial types When creating or loading datasets into an enterprise geodatabase, you can choose a spatial type by using a configuration keyword. Most supported spatial types have out-of-the-box configuration keywords for their use. IFan out-of-the-box keyword does not exist for a spatial type, you can create a new keyword that overwrites the GEOMETRY_STORAGE configuration parame:er. Migrating spatial types The Migrate Storage geoprocessing tool can be used to convert between different spatial types. You may want to convert your old ArcSDE compressed binary data to the new default storage type if you want to access the data through SQL. The Migrate Storage tool requires input datasets and an output Configuration Keyword that uses the chosen spatial type. The input datasets are modified, so you will want to back up the database first. Supported migration paths * SDE binary to Geometry * SDE binary to Geography * SDE binaty to ST_Geometry * Oracle SDO_Geometry to ST_Geometyamines & Figure 6.3 | When loading data, you can specify the spatial format to use for storing geographic data Spatial types Exercise 6: Work with spatial types In this exercise you will continue to customize the data-loading portion of the geodatabase workflow. Maintenance resonance [SS monagenet Another way in which you can customize how data is loaded into your geodatabase is to choose a spatial type. Spatial data can te stored in a number of formats. ArcGIS has default spatial types that uses for each RDBMS, but you can override these. In SOL Server, you have the choice of the SOL Server Geometry and Geography types, as well as Esti's ArcSDE compressed binary type. You will load point data into a feature class using the Geography type and learn how to convert your existing SDE binary data into a spatial field type. In this exercise, you wil * Load a feature class using the SQL Server Geography spatial ‘ype. © Migrate an SDE binary feature class to SQL Server Geometry. orLESSON 6 Step 1: Load data using SQL Server Geography When you use SQL Server for your geodatabase, ArcGIS creates feature classes using the SQL Server Geometry spatial type by default. @ Open SOL Server Management Studio and connect with Windows Authentication. @ In the Object Explorer, expand Databases > Naperville > Tables > gisowner.FEMAFLOODZONE > columns. ‘1, What data type is used for the Shape column? @ Open ArcCatalog, @ Expand your gisowner@Napenville connection and view the Properties for the FEMAFLOODZONE feature class, @ View the General tab. 2, What spatial type is used for this feature class? So far, you have created all data using the default spatial type, SQL Server Geometry. You will now create data using a nondefault spatial type, SOL Server Geography. In the Catalog Tree, expand Folder Connections > C:\Student\CMGD\ > Database > Elections. ® Explore PollingPlaces.shp. 3, What is its coordinate system? Hint: To find the coordinate system, right-click the shapefile, choose Properties, and view the XY Courdinate Syster tab. 68Spatial typos The SQL Server Geography type can store data only in a geographic coordinate system, which uses latitude and longitude to store coordinates. This data meets that requirement. ® Use conversion tools to import PollingPlaces.shp into your enterprise geodatabase. * Use the gisowner@Naperville connection. © Name the output feature class PollingPlaces. ‘* Expand Geodatabase Settings and set the Configuration Keyword to GEOGRAPHY. @ After the tool has completed, return to SQL Server Management Studio. @ View the columns for the PollingPlaces table. * You may need to refresh the Tables node. 4, What field type is used for the Shape column? You have now loaded data using a nondefault spatial type. Step 2: Migrate SDE binary data ArcSDE compressed binary data was used extensively in previous versions of ArcGIS, but spatial field types such as SQL Server Geometry and ST_Geometty have replaced SDE binary as the default spatial type. If you are maintaining an older geodatabase, you might have a lot of SDE binary data and may want to convert it to a spatial field type. @ Return to ArcCatalog, In the Catalog Tree, expand Folder Connections > C:\Student\CMGD > SpatialTypes > 9 xp patiallTyp LoadData.tbx. @ Run the Load Data model * Verily that the Output Geodatabase is set to your gisowner@Napenville connection. @ Expand and refresh the gisowner@Naperville connection. 69LESSON 6 The model places a new feature class in your geodatabase, called StateSenateDistrict. This feature class was loaded using the SDE binary spatial type. @ Return to SOL Server Management Studio. @ Refresh the Tables node. @ Find the STATESENATEDISTRICT table and view the columns. 5. What is the field type for the Shape column? @ In SDE binary, the Shape column in the business table of a feature class is an identification number used to link to feature and spatial index tables. Because the Migrate Storage tool updates the existing feature class in place, you would typically back up the database before running the tool. To save time, you will skip this step. @ Return to ArcCatalog, @ In the Search window, search for and run the Migrate Storage tool * Input the StateSenateDistrict feature class. * Use the DEFAULTS keyword. 6, What geometry type will be used when the DEFAULTS keyword is applied? @ Return to SOL Server Management Studio. @ Refresh the Tables node. 7. What is the field type for the Shape column in the STATESENATEDISTRICT table now? Close all open applications. pen appl 6-10Spatial types Conclusion In this exercise, you learned how to choose a nondefault spatial type for new data and how to migrate what spatial type a dataset uses. onLESSON 6 Lesson review 1, How do you choose a spatial type when loading data? 2. What advantage do spatial field types have over SDE binary? 3. What tool will help you migrate your old SDE binary data to a spatial field type? 612Spatial types Answers to Lesson 6 questions Exercise 6: Work with spatial types (page 6-7) 1. What data type is used for the Shape column? geometry 2. What spatial type is used for this feature class? SOL Server Geometry 3, What is its coordinate system? NAD1983 (GCS_North_American_1983) 4. What field type is used for the Shape column? geography 5. What is the field type for the Shape column? int 6. What geometry type will be used when the DEFAULTS keyword is applied? Geometry 7. What is the field type for the Shape column in the STATESENATEDISTRICT table now? Geometry 613Key terms roles users Configuring permissions Configuring permissions Introduction The bulk of the users of your geodatabase will be data users that will read and edit datasets, but not create or manage them. In an enterprise geodatabase, only the data owner has access tc the data until and unless the data owner grants access permissions :o data users. The easiest way to grant permissions to users is to group the users into roles and grant permissions to the roles, Topics covered * Operating system and database users * Roles * Applying permissions * Securing credentials Learning objectives ‘After completing this lesson, you will be able to: © Explain role-based permissions. * Create users and roles. * Apply permissions to datasets. * Explain how to safeguard logon credentials.LESSON 7 Figure 7.1 Data users are the least powerful but most humerous users in your sgeodatabase. 72 Data users ‘The last type of user in the geodatabase is the data user. Data users will make up the bulk of the users in your geodatabase. These are the end users that use and edit the data, but do not create or manage datasets or the geodatabase. Database ‘Admin User (sys, sa, postgres) Geodatabase *) ‘Admin User (sde) | | Data user responsibilities © View maps and data * Create maps * Perform analysis * Create and maintain features Data users can be further divided into readers and editors. But this distinction can be blurred because read-only or edit permissions are set at the dataset level. This means that a data user might be able to read only one dataset but will have permission to edit another. Data users in your geodatabase might not even have access to read al datasets.Figure 7.2 Connecting to a geodatabase using operating system authentication requires the Use of computer logon credentials Figure 7.3 Connecting to a geodatabase using @ database-authenticatod user requires a user name and password supplied to ArcGIS Configuring permissions Operating system users Users can be authenticated in the operating system or database. With operating system authentication, your user name and password (for logging on to the computer) are passed to ArcGIS and used to connect to the database. Operating system users are created and stored in the computer's operating system or the network domain. Database users The other type of authentication you can use is database authentication, When using database autheritivation, users log on to the geodatabase with a user account known only by the RDBMS, not the operating system. This requires users to supply an additional user name and password in ArcGIS to create the connection. User accounts are created and stored in the RDBMS. 73LESSON 7 Figure 7.4 Roles can be used t0 simplify permissions by grouping people who need the same access 10 datasets S ‘ArcGIS Help Library Tips for grouping usersin Geodata Table 7.4 Examples oles for Naperville 1 Roles Roles provide a way to group users based on shared responsibilities a Grant Select, Insert, Update, Delete Transportation On Roads To Transportation Using roles makes maintaining permissions much easier. Once you define roles and place people in them, you then give those roles permissions to appropriate datasets. By granting access to the role, everyone in the role has access. As personnel and responsibilities change, you can simply add and remove people from roles to grant or revoke permissions from the user. Defining roles For roles to be most efficient, you will need to put some time into determining what roles are needed and what permissions those roles should be granted, Roles might be divided based on job responsibilities or departments, among other considerations. For example, using the Naperville data, you might have the following roles and permissions. These roles can be expanded by dividing read-only and editing users. Role Responsibility | Grants Water Managing the —_| * Read and write on sewer Management | sewer network network © Read on flood zones, land use, and zoning Planning Maintaining * Read and write on flood zores, planning layers land use, and zoningTable 7.2 Configuring permissions Design roles Roles are the easiest way to manage permissions in your geodatabase. To set up roles, you need to determine how to divide your users into roles and what each role needs access to. 1. In the following table, record the roles you will need to create for your organization. After you have defined roles, note what datasets each role will need access to, and the level of access (read or read/ write) If you are unsure of your organization's structure and datasets, you can use this sample scenario, A local government is consolidating public safety data into a centralized database for ease oF access, Fire and rescue, police, and dispatch personnel will all use the database. The datasets include fire districts and stations, police districts and stations, live tracking on fire and police units (two separate feature classes), crime levels, hospitals, and basemap layers such as roads, lots, water, ete. Role GrantsLESSON 7 Table 7.8 Parameters forthe Ceste | Database User took Ss ArcGIS Help Ubrary Create Database Userin Geoprocessing 16 Applying permissions Creating users ‘The Create Database User tool can be used to creete users in your database or add OS users to the database without using RDBMS tools. To run the Create Database User tool, you need to use a connection to the database using database administrator credentials. Input Select a connection file for the database in which you database want to create a user. The connection needs to use workspace —_| database administrator credentials. CreateOS | SQL Server and Oracle only. Authenticated | Use to add an OS user to the database, The OS User user must already exist, Database User name and password for the user, either new to User and be created or existing to be added to the database. Password fusing an OS user, a password is not required. Role Optionally, the database role to add the user to. Tablespace | Oracle only. Name The default tablespace for the user, new or existing. If blank, the Oracle default tablespace will be used Geoprocessing or RDBMS tools? You can create users with geoprocessing tools or RDBMS tools. The geoprocessing tool makes creating a user quick and easy, but it does take default settings that you may want adjusted, For example, when you create a user with the geoprocessing tool, the user will have the permissions to create tables (and therefore feature classes) in the geodatabase. If you use RDBMS tools to create users, you will have full control over the privileges. Or you could create the User using the geoprocessing tool and adjust privileges in RDBMS tools.Table 7.4 Parameters for the Create Role tool Creating roles Configuring permissions The Create Role tool is used to create roles in the RDBMS. It can also be used to manage roles, granting the role to or revoking the role from a user. To run the Create Role tool, you will need to use a connection to the database using database administrator credentials Input Database Connection file to the geodatabase using the DBA user credentials Role Name for a new role, or an existing role to manage Grant To or Revoke From User(s) (Optional) Choose GRANT to add a user(s) to she role or REVOKE to remove a user(s) from the role, User Name(s) (Optional) Comma-separated list of users to add or remove from the role Assigning permissions ‘The Privileges dialog box is used to add users or roles ~ toa dataset and set select, insert, update, andlor delete privileges for the user or role. To grant privileges, connect to the database as the dataset owner. To access the Privileges dialog box, right-click the dataset and choose Manage > Privileges. 1LESSON 7 Figure 7.5 Sharing map documents and connection fils might Unintentional share credentials, as well 78 Securing credentials When you share map documents (MXDs) or connection files, you could be sharing your credentials with other users. Connection files, and connections embedded in a map document, can save a user's logon and password for later use. This keeps users from having to type their password for the geodatabase every time they access the geodatabase. But if a user name and password are saved, they will be shared when the connection or map document is shared. For example, if Jane, an editor, creates and shares a map document with Bill, a reader, Bill could connect to the geodatabase as Jane and acquire editing permissions. oe Jane Permissions: Editor | MxD, Aa | ver Bill Permissions: Reader ‘There are two ways to prevent this from happening. First, you can uncheck the box in the Database Connection dialog box to save the user name and password for the connection. If the user name and password are not saved, when a user opens the map document or connection, he or she will be prompted to supply logon credentials. At this point, Bill would enter his own credentials, connect as hirrself, and acquire only read access. The other (and potentially easier) solution is to use operating sysiem authentication for all users. By doing this, ArcGIS will always send the operating system credentials of the person logged on to the computer. Jane can create the map document and her credentias are passed to the geodatabase. But when Bill uses the map document, his logon credentials are passed instead.30 minutes Figure 7.6 Once data has been loaded into the sseodatabase, you must ‘grant permission for end Users to access it. Configuring permissions Exercise 7: Configure permissions for data use In the Naperville government, several departments need to access the geodatabase, but only to read or edit some of its data You will create roles for each department, assign users to roles, and apply permissions to feature classes to ensure that users can access only the data they need maintenance In this exercise, you will: * Create roles and users. * Apply permissions. 19LESSON 7 Step 1: Design a role strategy Before you begin creating users and roles and applying permissions, you need to design a role strategy. You will be creating three roles, WaterManagement, Planning, and Elections. @ Think about which role needs access to each of the following feature classes. 1. Enter the roles in the space provided SewerStormwater feature dataset (R/W) FEMAFloodZone (R) LandUseCurrent (R) LandUsePlanned (R) * ZoningDistrict (R) LandUseCurrent (R/W) LandUsePlanned (R/W) ZoningDistrict (RW) FEMAFloodZone (R) PollingPlaces (R/W) StateSenateDistrict (R/W) Step 2: Create roles and users Now that you have determined roles and what they need to access, you will create the roles end @ Open ArcCatalog. 7.10Configuring permissions @® Search for and run the Create Role tool with the following parameters: Input Database | admin@Naperville connection | Role WaterManagement @ Repeat the process to create the Planning and Elections roles. Next, you will create three users, one in each role. @ Search for and run the Create Database User tool with the following parameters Input Database admin@Napenille connection Database User pat Database User Password | pat Role WaterManagement @ Repeat the process to create users named kim and sam. © Place kim in the Planning role. * Place sam in the Elections role. Step 3: Apply permissions You are now ready to apply permissions to feature classes. 2. Which user account can set up permissions on a feature class in the Naperville geodatabase? @ Expand the connection for the above user.LESSON 7 @ Right-click the SewerStormwater feature dataset and choose Manage > Privileges. @ In the Privileges dialog box, click Add to add a user or role to the feature dataset. ialog box, you can see @ list of users and roles in the database. In the User/Role 3. Which role should be added to the SewerStormwater feature dataset? @ Check the role you chose above and click OK. @ Give the role Insert, Update, and Delete privileges. @ Click OK to apply the permissions and close the dialog box.