nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SQL and Server Update Questions

MyEthiopia

Hi,

I have a question regarding SQL Server. Our current environment is 10.7.1 for ArcGIS Server. We are looking to upgrade it to 10.9.1 to utilize parcel fabrics in ArcGIS Pro and give the department time to transition. Our current Enterprise SQL Server is on 10.4.0 which I believe is 2014. we want to utilize it for versioning and multi-editing parcel fabrics. We need to upgrade it to 2016, 2017 or 2019. Is 2019 a good start to have a smoother transition and allow us not to upgrade the server for a good amount of time. I'm confused on how to go about it; please give me your expert answers and another question is do we actually need a completely new dedicated SQL Server for Parcel Fabrics?

Find more posts tagged with

Enterprise geodatabase

Databases

Geodatabase Administration

Accepted answers

All comments

George_Thompson

I would look at migrating to SQL Server 2022, for the longest possible supportability; https://enterprise.arcgis.com/en/system-requirements/10.9.1/windows/database-requirements-sqlserver.htm

Here are some additional resources to help with this: https://www.esri.com/arcgis-blog/products/arcgis-enterprise/data-management/arcgis-clients-and-dbms-upgrade-considerations/

MyEthiopia

Thank you, the links are very informative. Makes my life easier. Do you by chance know if parcel fabrics needs to be on its own dedicated server?

George_Thompson

Not an architect, but you can have your parcel fabric data in the same Enterprise Geodatabase (EGDB) as your other data.

The biggest driver to have a dedicated server is the workload that is placed on the EGDB. If the parcel fabric work has many editors, it may be best to have a dedicated server.

Many clients separate the workload and to lessen any impact that 1 EGDB has on another.

MyEthiopia

Thank you!

VinceAngelo

You may need to time the upgrade process carefully, because I don't think it's possible to upgrade a 10.4 geodatabase directly to 10.9. You probably need to upgrade to 10.7 geodatabase first, then upgrade the SQL Server, then upgrade the geodatabase to 10.9. Even 10.9 is a couple of revs off current, so you might have issues using a modern Pro release with a 10.9 geodatabase.

- V

MyEthiopia

Thanks Vince, 10.9 would give us the ability to manage it from both ArcMap 10.8 and ArcGIS Pro 3.3. And when the time comes to upgrade our ArcGIS server from 10.9.1 to 11.0 or 11.3 it will still be compatible I believe correct? or do you think we might run into issues?

VinceAngelo

At some point, you need to leave 10.8.x behind. I'm an extreme late adopter, and I've been using Pro exclusively for years, even for hobby projects. Python 3 is worth the transition cost, and clinging to an unsupported platform is just no fun.

- V

MyEthiopia

Hi Vince, is this the issue your where explaining ? The upgrade should be from 10.4.1 to 10.7.1 (In ArcMap) then 10.9.1 in ArcGIS Pro 2.9 ? Trying my best to trouble shoot. Any pointers will be helpful 😞 https://community.esri.com/t5/geodatabase-questions/arcgis-enterprise-upgrade-status/m-p/1605250#M9558

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.