Working with a Multi-User Geodatabase

okay well hello everyone and welcome to today's webinar titled working with a multi-user geo database my name is Ian green Smith and I am a higher education analyst working in the educational research group out of our Toronto office so those of you who haven't attended one of our webinars before I'm recording this session and we'll make the recording that's a the PDF and a PDF of the slides and recording of the webinar available shortly after the webinar finishes this webinar will provide or its aims to provide rather an overview of the multi-user geo database and where it fits in the ArcGIS platform will discuss workflows and will allow you to provide access to the geo database by adding users and defining privileges through roles we'll also look at some introductory aspects of versioning and replication and overall this session will provide or I released I hope it will provide a clear benefit selves why you should configure your your enterprise to your database using using the things that we'll discuss today for your teaching and research some key terms that I'll reference during the presentation today are mercifulness at Enterprise geo database now the title of this presentation is a multi-user database and really these things are these terms are interchangeable it's the enterprise geo database is actually stored inside the database management system and is licensed through ArcGIS for server and a prized advanced a direct connection so geo database is one that is made using the database management systems connection methods and Direct Connect drivers in the client application now you don't need to worry so much about the backend of this stuff because a lot of them is actually a lot any connections that you make to a database will be made in the catalog window in arcmap or through our catalog and if you're starting to delve into pro that's great it's just that this webinar snuck in a touch on pro but the connection workflow of connected to a do database or an enterprise to name is rather a slightly different for pro a role in this context is actually what is defined by the geo database administrator and applied to users with very low level access users I think users are pretty self-explanatory they are the ones loading and editing data and have been assigned a role with a certain level of permissions geo database versioning which is something I'll talk about later on is it method by which multiple users can edit the same data without overwriting each other's edits or blocking others from reading it or writing reading it or editing the data so this is accomplished by using separate tables for each versions of data set to track edits as well as system tables to track different states of the data do database replication it's a data distribution method provided through ArcGIS that allows data to be distributed across two or more geodatabases by replicating all or even just a small subset of the data that you're working with ARC jism as a platform has a number of different components and for those of you who have attended a webinar like this in the past or been to one of our user conferences you've probably seen a diagram like this and as we start to explore the multi-user geo database it'll help us davin at least a general understanding of how things fit together across the platform storing your data inside the do database allows you to access your data across the entire platform meaning that you're not limited to the traditional desktop applications like arcmap or our catalog command that that you would normally use or traditionally use to manage your data create maps or even perform analysis this data can be published and made available to others via ArcGIS server or even ArcGIS online by the way of web mapping applications that can help extend the reach of your data to a much wider audience these same maps can also be consumed on mobile devices like tablets and smartphones for easy access on a modem mobile environment so while I'll just be focusing on the geo database and how it's possible to use it it's important to just keep in mind the end use or really the the end user if that helps but at the end of the at the end of the day it's really we're talking about data management and the geo database really forms a core in that in that sense the do database offers quite a bit of functionality and just highlight some key points on this slide here a lot of this functionality stems or it really includes storing of fundamental data sets such as tables for non spatial data feature classes for vector data raster datasets for storing or referencing imagery or continuing continuous data the database also provides behavior or ways to manage behavior rather through rules and relationships to maintain attribute data and data integrity it also contains tools to help maintain the integrity of spatial data by implementing advanced data sets like topology or geometric networks and even Network data sets the geo database can actually even store custom toolboxes so for those of you who do quite a bit of work with auto builder or do work with Python even all of those tools and scripts that you create can be stored within the toolbox that are stored within the geo database you can for those of you who do geocoding and you're not leveraging our chess online to do that if you have your own custom address locators the address locator and the network data set can also be stored within a geo database and the last point that make actually ties in really well so what we're going to be talking about today relates to scalability and integration a geodatabase can store and manage spatial data from the smallest project up to multiple terabytes of vector raster and tabular data so in doing so it supports a wide range of simultaneous users and editors so let's let's change gears a bit and in this first section I'm gonna start by providing an overview of the multi-user geo database discuss its role in the platform and then discussing lease at a high level the the installation and configuring process the setup and configuration of an enterprise geo database starts with configuring the database management system or DBMS client to work with with the ArcGIS platform this involves selecting one of the supported diva DBMS systems that integrate with our Jas and some are actually listed on screen not all of them because there are quite a few for the purposes of this webinar I'm going to show you how to configure an enterprise database using poster SQL but as important to note that any of the contact content and workflow that I show or cover can be applied to some of the other supportive database management systems now to add a spatial component to PostgreSQL you have two options namely using the st geometry or post GIS to handle spatial geometries built into data formats that were already comfortable using like shape files within the post grade database tables by default Enterprise geo database is created with within PostgreSQL are set to use the SP geometry and data type the post GIS geometry data type is included with post GIS and is actually a separate install post GIS follows those of you don't over plus GS follows the open geospatial consortium simple features specification for structured query language it also uses OGC well-known binary and well-known text representations for geometry within post great data tables so with the DBS installed and the geometry type selected we can now actually move on to creating the geo database one last thing I'll actually mentioned here the tool that you see on screen is one that I'll show you in the first demonstration it's actually only available if you're using the desktop standards or advanced license or if you've been using ArcGIS desktop for a while these are your arc editor and arcinfo licenses but the nice thing about tools being available like this is that they actually can be automated as well so ranging from creating video database to adding database users creating roles and so on everything can can be strung together but the geodatabase created we need to discuss how people are gonna connect to it and what level of access we're going to be granting them in our catalogs or even in the catalog window of death in arcmap we can generate enemy's connections and define database rules with relative ease did you create a database connection from the folder tree just you would just double-click it on the add database connection icon that's that's there and it's it's hard it's hard to see it now in the slides but oh I'll be able to show you when we switch over to the demonstration but once you double-click on it then the the images on screen will pop up and then it's just a matter of selecting the database platform so for what I'm talking about I'm already I know I'm gonna use post for SQL and then I need to define the instance so this can be this can be installed locally this can be installed on a on a virtual machine or a server so whether you have a fully qualified name for your server or even just the IP address that couldn't go into the instance authentication type this is where you are actually going to have to insert either your queue database administrator credentials or even the database administrator credentials and but and we'll talk about in later slides that that becomes straightforward but the point of this is just to identify that you know you really have to select a couple of key things the database is going to be using the instance you're going to connect to at what level you're going to connect to it and then the last one is actually choosing the database which actually becomes a drop-down menu so I've mentioned a few of these positions or users within the database already but for clarity it's really necessary to define the different types of users within a multi-user geo database because they're different than what we're traditionally used to really if we're using a file geodatabase we're working with cad data or working with a shape files or text files for that matter so at a high level these include the database administrator the geo database administrator the data owner and the data user the database administrator in this case because we're using post grady SQL is created by default when PostgreSQL is installed on the server so the user name is post gray or Postgres responsibilities for this user or this role include creating the database creating users and creating their roles granting they can grant permissions but it's not restricted that's not restricted to them but they can also configure how data is stored within the geo database the geo database administrator or as i created when you this one can be created rather when you're using the create Enterprise geo database tool as I showed you in the previous slide this account can be considered one of the most powerful accounts and the geo database and it actually shouldn't be assigned to a single person I wasn't what I mean by that is that by giving multiple users access to the geo database through this SDE orange geo database and an enroll it's a good management tactic to control for project workflow employee turnover or the with regards to student research and student projects think of student graduation vacation and so on the responsibilities for this user include performing maintenance maintenance tasks managing at the top level or default version of the geo database the data owner this user account is used to load a data into the database and similar to the geo database admin this account is also not typically assigned to a single person as multiple groups or departments within within a school or municipal environment or that regardless of where or where you work may need to be able to load data into the geo database and that's really what this this users you that user level is used for so in addition to loading data this this user can manage user permissions fields indexes and even register data as versions and I'll talk about that in our second demonstration and lastly the data user and these are the ones that make up the bulk of all of the users in the geo database so whether it's cam krysta jonathan ian brandt whoever that they're all they're all names who has been given explicit access to the geo database and it's it's us that really are the ones doing a lot of the editing report generating creating maps and so on so with that I just want to jump over to our catalog and just actually before I get there it's going to show you a couple of things just to keep in mind when you want to go and set up an enterprise geo database as well as configuring access for others now I realize that not everybody would have access to this my ESRI portal especially if you're a student within within a university or college but for those of you who aren't or those who do actually have access to the my ESRI account this is for the coming of age for a lot of students software companies and software is really becoming become available to download so this is where if you have desktop er or pro or server for example you would come here as the site license administrator that isn't one of controls access to the software you would come here access the data I did it that we include the software as well and download it so as I mentioned Enterprise geo databases are authorized through our chests for servers so I can click on this I can download all of the relevant packages that I need for ArcGIS server there's even stuff related here for for portal as well what i want to draw your attention to is it's actually not on this initial page we'll go to the additional products tab this is where you're actually going to find the client either database clients like like post gray so we have we actually host and allow you to download the Davis clients for Windows and Linux for the different supported versions of of post gray but we also do it for for Microsoft physical server Informix and and so on there are a number of other ones here that we host so if you're looking to do this this is something that you're going to have to keep in mind you're going to need to get access to specifically if you're using sequel server however if you're if you are keen to use a PostgreSQL database with what they're really serves 10.3 so we're at version ten point three point one right now but they're released a ten point three the client libraries are actually included with with the install of our j/s server so there's no reason there's no need for you to download them which is actually quite handy so let's go ahead and get that out of the way I'm going to go to our catalog so here in our catalog or you can do the same thing in in in the catalog window for for arcmap I just wanna show you this the the tool that I've been talking about so this is a my search for the crate Enterprise just like this in it'll bring up lift the tools here well I draw your attention to is this create Enterprise geo database tool now firm to sit a bit of time for any demonstrations that I'll show wise pre pre created a lot of this stuff but you can see here that I can actually choose one one of three options here so I'll choose my post gray geo database I my instance so my my multi-view there is I have installed locally so if you're going to do that you can just type it's actually easy to just type in localhost but again in this installed a server or on a VM somewhere the IP address will work will work just fine you'd put in the name of the name of the geo database you want to provide you would authenticate into it so again the database administrator this is a person who can create the database this is so you need to authenticate it to that a product of creating the geo database through this tool is that the geo is geo database admin username and password so ste here is creative and then you would you actually use your your authorization fathers used for first server to create the geo database so again I've done that and just saved a little bit of time because not so much in terms of creating the geo database but in terms of loading data in generating connections and so on but it's it's useful to know how to do it and this miss search tool takes takes a lot of the guesswork out of remembering where some of these tools are so I've got a few connection files here and your database connections are all stored in one common area so you're you're used to searching for or creating folder connections here under your folder connections just below that are your database connections and to create a database connection you just double click on this just as I described in the slides again you choose your database decide where it's going to go set up your username and choose your database and you're off to the races now I didn't mentioned a lot of stuff I created ahead of time so what I want to do is actually want to connect as the GIS owner and what you'll see is that I actually have a lot of data already pre-populated this within the geo database now because I'm the GIS owner I have full control over this data I also have full control over who accesses it now what I've done ahead of time is that created a planning role and a role is created through either a geoprocessing tool or you can actually add right click on on either the the SDE or the DBA connection and generate enroll that way but again I've created the tool head up there created the role ahead of time but what you would do is provide that DBA or post gray connection typing your role and then yeah alternatively or optionally rather you can choose to assign it to a specific person so I have and I'll show you this when I switch over to the database client I've created a few roles but just for the sake of example it's going to drag my my DBA connection in here I'm just going to call this parks leave the username blank and you're not going to see anything fancy but you are going to see that it's been completed so what this means is just just like your IT group when there's a new hire when they're trying to configure access to certain applications that some people can access and have access to and some people can't well they do that through or one one of the mechanisms they can use to do to control this head stuff is through a role so in this case in this case it's a group or all of that I was referring to so I've got what I want to show you next is that how we can actually in the tool box I want to go to data management tools our geo database administration and this is where a lot of the multi-user geo database tools exist what I want to do is I actually want to create a database user now I can I can open this tool or alternatively I can disconnect from here double click into the DBA connection go to admin and actually just add a user it actually opens the exact same tool this away from my computer to to wake up here we go so I've got my database connection here that's already there I'm going to this is I'm going to actually create a database user in this case it's going to be Christa Christa access can I give it a simple password that she can create later and here I'm actually going to sign it assign it to a group or also this I'm going to assign her to planning and I'm going to click OK and that goes relatively quick as well now what I want to do is I want to add that database connection for Christa here just to show you how it works so I double click on this on the idea that database connection confirm the following but we're not working with this user I'm R so you're going to connect as Christa Christa and this is where I can actually select any of the geo databases that have been created and that live on the localhost instance in this case I'm working with the camp data from Kamloops BC I'll click OK and you see the connection file has been created that's the best practice it's worthwhile to actually to rename this so what I'll do is I'll just show you how at least how I like to do it that way it's easy to keep track of in that way you're not just looking at the same thing connection it's just broad connection files but here I want to show you a couple of things the first one is yes it's a unique it's a unique connection and it stores Christa's information this connection file could actually be shared as well but because Christa is actually part of the planning role Chris has only been assigned privileges to two specific datasets so while the GIS owner can see all of this data that's here a relationship classes associated with that idea if I disconnected just clean this up a little bit my connectors Crysta you'll see here that I'm that as the GIS owner I've configured it so that all the planning role can only see data that's stored within the assessment feature data set so here we have a topology and a property's data set and then my buildings data set so just to reiterate this is all controlled through through rolls and just to show you what it looks like it had been up a different environment before I switch back to the slides so let's show you PG admit this is this is a database client that comes installed by default with PostgreSQL so I'll just I'll just authenticate in here my password and it's actually the layouts very similar to our catalog here just want to draw your attention to the databases column so here I have your post grade database that's one was created by default the enterprise cue databases that I've created I've created one here just for another application that I was working on as well as this canvas BC so I can double click in here I can review some of the items that are in here all of the users that are assigned to has assigned schemas but I don't really want to spend time looking at the schema here what I want to focus on here are the group roles and the login roles so the group roles I created the parks role for you but the planning role is what I use to assign Christa to as well so there's an actually I can even click on this I can I can find out more information about it I can see who's actually members of this specific roles and so on so with that I'm just going to switch back to the slides here and and we'll move on ok so in this next topic we're going to discuss multi-user editing workflows in the Jew database and specifically we're going to be focusing on reversing absolutely who attended the or listened after the facts of the previous webinar that I gave I aligned and apologized that this is a bit of review for you but I outlined the this really there are three common geo database types the first one is that Microsoft Access based database that we refer to as the personal geo database the second one is a collection of files and a system folder that's stored on disk we refer to that as file geodatabase and that actually represents an evolution from from the personal geodatabase and the third one is the enterprise are tested ADA base which is a collection of tables views and functions stored inside a DBMS now the file and personal geodatabase are most similar in that they're both designed for single user editing however the file geodatabase is recommended over the personal for its ability to handle larger data in terms of size fame its ability to handle multiple users it's also possible to have more than one editor at a time in the file geodatabase provided that each user is editing a different feature dataset or a standalone feature class or tables within the geo database however it really as the title suggests on the slide challenges arise with this editing approach to protect the data stored in the geo database and help manage it geo database locks are created as you interact with the database to ensure that integrity to ensure integrity for transactions and there are two basic types of geo database locks one feature locks and future locks prevent multiple users from editing the same feature and overriding one another's changes think of this no like a Word document or Excel spreadsheet that's saved and shared on a network server that that's already opened and being edited by somebody else if you try to open it you're going to be prompted to say that someone so is using it yeah you're asked to wait your turn or notify them the other one our schema locks of schema locks maintain the consistency of the table schemas while the tables are in use so the purposes of this webinar we're just going to focus the discussion and demonstrations I show around the version editing workflow so versioning is something that's built that is accessible and possible to do only within an enterprise in your database so what is what what our versions multiple editors and transactions can be accommodated through an editing workflow that employs versioning of version represents a snapshot in time of the data in a geodatabase and that is data that is registered as version within the geo database it's important to note that versions are not copies of the geo database either but rather there are separate views of the data well any transaction that takes place in that person that is tracked in assistant tables of the geo database when working with enterprise to your databases that have involved multiple users with varied roles its general regarded as a best practice for users to access data through a person anyways the version an individual accesses is predetermined by the permission level granted by the database administrator or as I'll show you it said you can control access through yes you can could the database administrator controls permissions but it's ultimately the the data owner who controls what what data that you can actually see and what data you can actually get to so when data is registered as versioned to tables or to Delta tables are created a for adds and D for deletes and they're created to track insert update and delete operations I've done the data so really in an aversion data set what it actually consists of the original table plus any changes made by each user they're stored in those Delta tables a typical workflow for setting up versioning or consulting and it's across versions and maintenance in the geo database can look like what time what you see on screen if you work your way from left to right you really start by registering the data as version now I don't know it sure is that sunk in in the previous slide but that's really a key component the entire geo database can be registered as versioned but more often than not you don't need access to the entire geo database you just really need access to let's say for the sake of example two or three data sets but feature classes rather than are stored within it so so long as those two or three feature classes are registered as versions you can have access to those and solely work within those so that's the first thing you do you register the data is version that's typically done by the data owner the next thing you do is that you create a new version once it is registered version registered as a version a new child version can be created that branches off of the parent so I'll refer to this notion of parent and child it said actually it helps as opposed to supposed to origin a destination for example when created this version is identical to the parent but over time it's in any version that actually branches off of that child will change the the middle one this is this 1/3 or purple from a box this is really something that we're already comfortable with so this is identical to non version editing so it's something that you you add a shape files or to this personal personal or file geodatabases you can't be anything merciful is identical in this sense but once you are done your edits the next thing you need to do is you need to reconcile your edits so that is reconciling edits that you make in the child back to the parent so a parent is what you branched off of so you and so the term is called reconciling and posting so reconciling and posting changes integrates your edits into the parent version when you reconcile all and it's in the child version so what you've wrenched off and use are compared to that of the parent version and that's what you actually want to merge them back into if there are any conflicts those conflicts are flags for review now conflicts can come up there beyond the scope of what we're going to be talking about today but for the most part if you are the only editor and depending on your reconcile and posting workflow you won't run into conflicts conflicts typically arise when there are multiple child versions that are being reconciled back to one parent and edits have been made on similar features the last step here relates to analyzing and compressing a geodatabase so this is something that you may you may see the option when when you're working with geodatabases or the file geodatabase for example but really this helps improve the performance of the judea's so as child edits get posted to the parents to the parent over time it can be beneficial for the child version to compress the geodatabase and ultimately speed up the performance what you're doing by compressing is you're removing all of the states so each time you add a feature you something two attributes that adds a state in the state lineage of your versioning tree compression removes that and once you've posted your changes you can actually get rid of your your version altogether because it's all being consolidated and posted back to the parent and and move on the last step that I mentioned is analyze so whenever you're working especially with an enterprise geo database in terms of indexing it's important to have up-to-date database statistics and each time it's run it just helps to helps the software reference update statistics that can help really it really improves the geo database performance so there's a lot to really digest here here on the slide but it really starts by registering the data's versioned creating the version going through a simple editing workflow reconciling and posting your edits and then really compressing and analyzing the geo database to help improve performance and speed up indexing so why use versioning what are some of the reasons that why you would use this workflow so let's say for the sake of example that I work in the planning department for a municipal government where we have parcels for the miscibility that are available online for the public to see however the department I work it receives daily applications for submitted development with versioning it's possible for the public to view if the official parcels while another version exists for the planners to work with versioning can also be useful to model what if scenarios such as flooding a separate version in this context would allow individuals to work with the same data for the forum analysis that cannot be seen by other versions until the project is official versioning also lends itself to allow for multiple stages of the project such as to keep track of multiple stages of the projects such as roads over over a given period of time bill determine what roles are different by specific versions created in specific years another way to look at that specific example is to incorporate you add enemies to incorporate archiving but that's really beyond the scope of this webinar but what about to do is almost switch back to respect the arcmap now and I want to show you a little bit about show you a little bit of versioning before we before we move on to our lot of topics okay so we're here at heart map and in the catalog tree I have my I have my database connections here what I want to do is just gonna refresh them because I want to bring in that that Crysta connection here and you'll notice that if I actually go into the crystal connection here and access the data if I right-click on it there's there's interesting content that comes up in the context menu now because I'm just a data user I don't have access to a lot of this information so a lot of its grayed out but if I actually connected by disconnected from this user and I checked this a jeaious owner I have I will be able to see this quite a bit of the information available to me specifically wanna draw what I want to draw your attention to is this option that's grayed out so I remember one of the first steps is to register or is the data that you want to work within a specific version as version so I've gone ahead and done that I've done that specifically for the properties data set and I've also done this for a building's data set so you see that as grayed out I also have the option to to unregister it I also can restrict who has access to this so I talked earlier about that here I have a couple of roles one my planning role so this is where cam and Christa can actually access specific data sets and I also have a GIS group role as well but I'll just call this connector from the gs1 and I'll reconnect to Christa I'm going to add I'm gonna add this data in let it come in stay in the drawing order a bit I'm gonna go back to the source tab so here I've connected I have a database connection as as Christa but look at the ones our attention to is here in the source so here I have my my default so this is this really is the highest point of the versioning tree this is the there is there is nothing about this this is kind of your state zero if you will but what I can do is I can go in and I can either I change versions or I can create a new version as I mentioned to save it a little bit of time I've created some Korean versions ahead of time and you can see who who owns them as well and that's that's really a something that's quite useful in the judaize administration side so you can see here that the default version is owned by ste the GIS owner that I've been doing a lot of showing I showed you lots up with that it was created a number of versions here and then our ste G base Minnesota has created the publication version as well but what I want to show you here is how we connect to this specific version and you'll see here that now it says who owns the version and then the name of the version it's still tied to the instance but what I'll do here is I'll just I just have a quick bookmark here and what I want to show you is that I can start an edit session right now I'm editing and what do I do is just within this version the same for the sake of example we've received instructions that these these two selected parcels are to be merged so I'll do is I'll just select those two and then from the editor toolbar select merge I'm going to be prompted which which partial should be merged into when I merge it into the one on the bottom that's P six to eight to four I'm gonna click OK sort of my selection now what I'm gonna do I'm gonna go to my my versioning toolbar and it's it's docked up here in my in arcmap here but here this is where I can actually review any versions that that have been created so just just like I was showing you earlier if I wanted to create a new version I could create a new version using this but what I'd like to do is I want to I want to reconcile my edits so that's reconciling my edits back from the staff back into the parents of this staff version which happens to be the planning version so what I'm going to do is I'm just going to click reconcile it's gonna ask me how do I want to handle reconciling the changes that I've made specifically I want to reconcile in favor of of the targets that's in favor of the child really that that I'm working with so I'll click OK so what that does is it compares what is in the child to what is in the parent and what is in the parent and once once that's gone through and no content conflicts have been detected then this icon here will be will be visible that's post your changes and it's as simple as that now if I were to switch versions out into into the planning version I'd see that that that this that this change has been made as I mentioned before I'm not going to be touching on conflicts but in general complex can be detected when you reconcile with a target version under the following instances so the same feature is updated in both the current version being edited as the target version the same feature is is updated in one version and then deleted in another or even if you're working with advanced data type select apologies so a topologically related feature or even ever even a relationship class is modified in a current version being edited and the target version so it conflicts really can we can quite complex but the concept of registering your data is as versioned doing your edits reconciling your edits and posting your changes that is actually quite straightforward and that's really what I wanted to get at in this second demonstration we'll just save my edits and then I'll minimize this and we'll get back to our slides for the littleness of the last part so as we discussed in the previous section the efficient management of an enterprise geo database that is accessed by multiple users with readwrite access is greatly assisted through the use of versioning in this last section I'm going to try to build on the concept of bursting and by discussing a form of data distribution that's a term geo database replication and demonstrate how through a replica you can manage a workflow of distributing data to users outside of your organization or even outside of your school or outside of your network so do database replication is the data distribution method used share enterprise level data within the ArcGIS platform it's built on top of versioning so data needs to be registered as versions and they've in order for this to work replication supports the sole geo database model as well so that includes topology networks and behavior rules and relationship classes as well where any data conflicts are resolved prior to committing changes back to the parent replicas this replication type is also loosely coupled which means that a replicated geo database can work independently from its parents and any edits can still be synchronized similar to registering a database as version when all or part of a version of a data set are replicated a replica pair is created one replica resides in the original geo database that is the parent and their related replicas is distributed to two different geodatabases in this case a child or multiple children depending on the replication workflow chosen it's possible for any changes made to the replicas and their respective databases to be synchronized so that the data and one that replicas not just that in the related replicas it's important to note that I feel like a broken record sometimes but it's important to note that the data it really doesn't need to be versioned in order to serve this to work so if you're trying to go down the replication path and you're not you can't figure out why icons aren't showing up in the distributed database toolbar for example that's because a lot of us stuff is tied to not being registered its version in addition to that your de that must have global IDs now depending on the data model you're using like if you're using the Canadian municipal data model for example global IDs are built into the data model so we said that it's imported that global ID will be assigned will be assigned to it it's not really anything you need to worry about that because the data models got to take care of it for you or you can actually manually add global IDs and I can show you how to do that there are a number of different scenarios of where replication can be useful in that and I can I'll include that link to you when I send out the slides and they're recording but in terms of replication types there are different options to consider on how you want to replicate your data they can all be done either connected or disconnected environment and all of them each one require the parent at least the parents to be an enterprise ste but geodatabase the first option is check-in checkout this allows you to edit data in the child replicas and synchronize these edits back to a parent replication in this case only occurs once and when the edits are synced back to the parents then the replica is discarded they that like a favor like a temporary connection or even even this phone call I'm transmitting information to you over the phone as soon as I hang up the phone there's no more connection check-in/check-out second option is one-way replication that's the one I'm going to show you and this is ideal if you have a scenario where you have a production and the publications you database the one-way replicas will allow you to send the edits multiple times which is a big advantage over the chicken checkout method to the other two databases and allow you just connected to those to your databases to use them so one way child replica is considered read-only and and that's really a one downside is that you can't sync it back so you can't make change to the child and push them back to the parent but that's really the arguments using the last type of replication and really it's the most powerful since you can make edits to either side so that's the chair the the child or the parents you database of multiple times and synchronize the changes back and forth between them this is called two-way replication is useful in situations where multiple editors are law editors are located in different offices those changes can be sent from satellite offices for example back to head office and vice versa all using the exact same replica the hook would this one this last replication type is that both since your databases have to be mark ste order to Enterprise geo databases for it to work so with that at the time that I have left let's let's jump back over here I've got to do um XD's here open one representing my my parent replica if you will and the other one representing my child and what I want to show you is not so much how how the replicas are created that's actually quite easy quite easy and quite straightforward to do just through the distributed database toolbar here and a lot of that becomes unlocked as soon as data becomes versions but what I'll show you is the source so here I'm in my parent and I see I have my buildings and my property on an area of interest here I have the version I actually tried to draw your attention to this earlier so this is the version is called publication and it's owned by the geo database administrator so that's the parent on the other side I have the child the child is actually just a file geodatabase that's stored somewhere on desk so for the sake of example what I want to show you is how using a one-way replication workflow users who have access to the production geo database that is the enterprise geo database can load data and then sync that data with satellite offices or or contractors or people just working off the network and to do that I'm just going to go back to one of the first tools I introduce you to and that's that's the that's be a pen tool I introduced you to you in the in the in the previous webinar so my input data set here just gonna browse to it I just have a building's shapefile here click add my target data set is actually my buildings data set that's already inside the map those of you are familiar or with using the append tool you have the option to force it to check the schema in this case I know that the data that's being upended the schema or gmat already matches so I'm not going to bother testing it and I'm just gonna click OK the tool is going to run the data is going to be added into the map in the designated area not what I can do is once that data has been been added and I'm not in an edit session either once that date has been added I can actually go here to my distributed database toolbar I can synchronize my changes so again I'm working with another price to your database on the left hand side and I'm gonna push these changes are in a sync these changes to the replicas that lives within a file geodatabase this is just done by clicking on synchronizing changes you can select just to just accept the defaults here click finish I'll refresh my screen and here you can see that data from the replicated geo database the enterprise-d device has been pushed to the file do this and that's really what I wanted to show you but you remember that this is this is one way if I if I had configured an ste geo database or enterprise database rather on the other side I could have appended this data pushed it out to the other one made an edit for example whether it's to a building or to a parcel and push that back and everybody would have been able to see it but conceptually that that is geo database replication so with that just switch back to our slides and let's wrap things up so in summary I've gotten a little bit longer than I wanted to but in summary we've always covered over the last hour we learned about some of the fundamental aspects of the month user geo database and I think there there are a lot of key points here first you know we we looked at where the multi user database sits in the ArcGIS platform we looked at creating any Enterprise geo database and configuring access through database users roles and connection files and find that we looked at version editing workflows and and David distribution methods for geo database replication if you want more information on this a really good starting point that is actually available right right online and what used to be the resource the arcgis Resource Center is now kind of divided up but the links here you'll have when I send out the slides first one gives a really good tour of the Geo database there's also a file geodatabase tutorials and the second one actually touches on a lot of key aspects of the enterprise geo database or working with an enterprise geo database but this in this case you're not working with a full Enterprise geo database you're going to be working with sequel server Express but versioning can still be done with it and an archive archiving customer and it's oaken replication so there's a lot or a replication can be incorporated with with this so a lot that can be done with these two links so something that's a little bit more homegrown some Canadian examples I really invite you to check out our lesson planner and if you weren't already aware you'll find a wide range of learning resources and that really relate to what we've discussed today whether you're looking for desktop online or solution focused resources you can use the tool that's available through the link on screen to quickly search and find what you're looking for a relevant example of this are the geo database labs that I created last year actually that covers quite a bit of the material that that I covered today now those were created for ten point two point two so that some stuff has changed a little bit but a lot of the core concepts still apply and what's really great about this lab series is that it uses the Canadian municipal data model amend earlier and focuses on file geodatabases as well as Enterprise geo databases so on behalf of ESRI Canada I want to thank you all for attending this webinar please please feel free to contact me at any time I my emails are on screen and I'll make the slides and recording available shortly after the presentation fishes so thanks everybody

Channel: Esri Canada Higher Education & Research

Views: 13,149

Rating: 4.8130841 out of 5

Keywords:

Id: ibGC6ycA_9Y

Length: 60min 47sec (3647 seconds)

Published: Tue Nov 22 2016