GeoEvent SQL Server database - best practices to handle volume

Question

Hello,

We are looking for guidance regarding a geoEvent SQL Server database.   One ESRI demonstration video said that if we have moderate to large volume, best practice is to have a separate server and that hundreds of events per second is ???moderate??? volume.  Is there literature for best practices guidelines for setting up our servers with regard to transaction volume and types?

Thank you.

MarcoBoeringa · Answer

We are looking for guidance regarding a geoEvent SQL Server database. One ESRI demonstration video said that if we have moderate to large volume, best practice is to have a separate server and that hundreds of events per second is �??moderate�?� volume.  Is there literature for best practices guidelines for setting up our servers with regard to transaction volume and types?

Yes there is (well, at least for ArcGIS for Server's most used service types, I don't think it gives any specific guidelines for GeoEvent processor yet) :

ESRI System Design Strategies webpages

There are even Excel spreadsheet tools there for doing preliminary calculations (see this page about the Capacity Planning Tool), but it probably requires the accompanying book to effectively use them, as there is a ton of options in there.

The benchmarks for certain hard- and software configurations listed on the System Design Strategies pages will be of help too though...

AdamMollenkopf · Answer

With moderate volume, the best practice recommendation is to have an ArcGIS Server that is dedicated for GeoEvent Processing and another (or cluster of) ArcGIS Server that is dedicated to hosting Feature Services, Map Services, GP Services.  Doing this helps isolate stream processing on GeoEvent Processor from other GIS services and allows GeoEvent Processor to have full access to resources on its isolated instance.  The role of the EGDB (Sql Server) would be to back your Feature Services for persistence.

Does this information help?
Adam Mollenkopf
ArcGIS GeoEvent Processor for Server - Product Lead