Does anyone have a best practice when it comes to dbms and versioning gdb's? I have done a considerable amount of research but there is so much info it is hard to get a clear cut direction on how to accomplish this. I have messed around with SQL Server and created a test db to connect to through my client computer but I still feel like I am missing something. Thanks in advance!
Mat
Anyone? Ultimately I want to be able to constantly update and version a gdb. It will be used to dynamically update a custom webapp among other things. I have SQL set up on our server with ArcServer. Any help is appreciated!
What is it you're asking? I've been using a versioned Sql database since version 8.3. Not sure if the practices that work best for me would work best for you. If you could be a little more specific, I might be able to give you a "been there, done that" sort of list...
Thanks. That is exactly what I am looking for. How to version a Sql gdb. I have Sql Server 2014 installed already.
Please provide the configuration details that you are using (ArcGIS Desktop version, DBMS, etc)
As Joe mentioned, you need to provide more information as to what you are looking for, before someone can provide you with valid information
ArcMap 10.2.2 and SQL Server 2014. What other information do you need?
Have you installed ArcGis Server and the SDE portion of it? My suggestion is to contact support. I cant walk you through a complete install while pecking on a tablet...
I have installed ArcGIS Server but not SDE. Was unclear if I needed SDE or not. Where does that get installed? On the server or my client machine?
SQL Server 2014 is not a supported DBMS version for 10.2.x:
System Requirements
Starting form 10.1, installation of ArcSDE is only required when you plan to use ArcSDE Command line tools or the Application Server Connection. So I don't think you need to install it for this.
I need to confirm something, as I am a bit confused.
Mathew Suran: Are you discussing about
Thank you for that info. I am new to gdb management so I am not sure if I will answer these correctly.
1. "Registering as Versioned"-Don't know what this means. I don't have SDE installed.
2. Don't have SDE installed.
3. I think this is what I am looking for.
To clarify, I have created a gdb in ArcMap 10.2.2 Catalog with 214,000 features. Since at this time, anyone can edit (and potentially delete data) the gdb, this is a problem that we are trying to address. I have been looking for the best way to accomplish this task. From what I gather, we need to create roles that have admin/edit/read-only capabilities to be able to keep track of when/who made changes and to allow us to have a rollback feature for "accidents".
It is my understanding that this is where versioning the gdb comes into play. I could be wrong, but from what I read was that I need a database management system, ex SQL, postgress, etc to be able to maintain multiple versions as changes are made to the gdb. I chose SQL based off of ease of use recommendations. I have installed 2014 SQL Express (which is free, but not supported as you stated in the previous post which I will change). I have not been able to figure out what to do next which is why I am here. I am looking for a workflow to explain what I need (as stated in the begining) to accomplish what we are trying to do. I hope this helps.
We have ArcMap 10.1 and 10.2 on numerous machines in our office with a single IIS Server machine. That Server hosts ArcServer 10.2.1 and SQL (don't know if that is best practice). My machine/role is admin for the server and gdms.
Just wanted to follow up with any more assistance or advice you can lend ASenGupta-esristaff. Thanks!
You don't need ArcSDE installed for 1 and 2. You just needed an sde geodatabase.
What you described in the last post is actually pointing to Point #2 (Creating new Versions in the sde geodatabase?)
I would suggest you go through these links to get a good idea about the Versions and different scenarios where they are used:
What is a version?:
ArcGIS Help (10.2, 10.2.1, and 10.2.2)
A quick tour of versioning:
Version scenarios:
In short, each Version in a geodatabase is a Virtual Copy of the data present in that geodatabase. Each editor\viewer can be assigned a different version, with Access Level of the version set accordingly.
Hope this information helps for now.
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
