AGRC is getting ready to load our Utah PLSS Fabric into our SDE, from a local geodatabase.
What should my database team know before we start and what are the procedures to do the move?
Could not find documentation on ESRI support yet, maybe there is not one, is it more common to build it in the SDE rather than creating it outside then move it?
Inquiring minds want to know.
There isn't a specific procedure for Parcel Fabrics versus any other complex geodatabase object. Make sure you have a clear understanding of the requirements needed. There are a few things I would make sure to check and go over before making the transition. You can simply copy and paste the feature dataset from the File Geodatabase into the Enterprise Geodatabase.
1) Make sure you know what geometry storage type you want to use. 10.3.1 Defaults are ST_Geometry for Oracle and Geometry for SQL Server
2) Understand the versioning structure with Parcel Fabric editing. Parcel Fabric editing only supports child versions off of the Default version. Grandchild versions are not supported for Parcel Fabric editing.
Also important, Parcel fabric versions and edit locking found in the documentation below.
3) Just like any other large data format in an Enterprise Geodatabase, it is crucial you stay on top of reconciling/posting versions, compressing the geodatabase, rebuilding indexes, and analyzing datasets.
That is a lot of documentation, but feel free to post any questions here and we can get a discussion going. Hopefully that helps out.
Senior Geodatabase Support Analyst
Not to hijack this thread, but I was wondering if there were recommendations for item #3, specifically in regards to Reconciling and Posting. For example, if one has a version that will be in use for several weeks before it is Posted, how often should one Reconcile that version before the final Reconcile and Post, given that several other versions may be posted in that interval?
Chris Donohue, GISP
I was curious if you had any feedback on the overall performance of the parcel fabric in SDE (SQL Server 2014) using the GEOMETRY storage type at ArcGIS 10.3.1? Our team is currently testing this and preliminary findings reveal that performance is comparable with ArcGIS 10.2.2 using the SDEBINARY storage type.
I can't figure out why i'm getting this error when copying a parcel fabric from a fGDB to SDE. Here are the steps I take.
1.) right click on the fGDB feature dataset containing the Parcel Fabric and select copy.
2.) go to SDE and right click on the geodatabase and select paste.
3.) when the options dialog box opens, select the parcel fabric and, for ALL feature classes in the Parcel Fabric, select the configuration keyword of SDEBINARY.
4.) click ok and allow the feature classes and all domains to be copied into SDE.
I've tried this on my existing SDE database and on a newly created database. I can copy and paste other data without any problems.
I haven't tested this on my end, but try pasting the fabric into a Feature Dataset within your SDE database. For some reason I feel like it's a requirement that the fabric resides within a feature dataset. Maybe you already tried this but based on your post it appears your were pasting into the root of your database. If this still doesn't work then it's most likely permissions within SQL server...