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; } } }

Single points of failure with enterprise geodatabase

ShannonSmith5

How do you avoid single points of failure with an enterprise geodatabase. We have a production geodatabase and publication geodatabase. We do have a solid backup and recovery plan in place and know how to use it. How do you keep your publication geodatabase constantly updated. It gets updated every night but in some cases that is not enough.

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

George_Thompson

What is the RDBMS being used for the enterprise GDB side?

You can write and schedule Python scripts to update your publication database on a schedule. It would be based on the volume and how often the records would need to be updated.

ShannonSmith5

SQL Server database, 10.6.1. These updates can occur when people are connected to it?

George_Thompson

Depending on the data and locks, yes. I am sure that many people here do this workflow. You would need to look at what is needed and build a script and test in your environment.

You may want to look into this with your DBA team to have better redundancy of the EGDB: Connections to highly available SQL Server databases—Help | ArcGIS Desktop

ShannonSmith5

Great, thank you for this.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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