We have a central table (stored in SDE within SQL Server) containing ~50,000 points. This should more or less be distributed through Server as 50 separate services containing 1,000 points each. We have a web front end based on the JavaScript API that we use to access the services. There seem to be 3 basic ways to do this:
Acknowledging that every implementation is unique, are there any rules of thumb as to performance, resource allocation, etc. that would make any one method better than the others?
Thanks.
Kyle:
I don't get it. Are you limited to serving only 1,000 points per service or per layer within a service?
Joe--
Sorry, no. Basically we have a lot of similar data that pertains to many different clients in many different markets. So I want to serve up Client 1 in Market A as one service, Client 1 in Market B as a second service, etc. So ultimately I need to break the larger dataset into pieces for the end user, I am just trying to make sure we use the most efficient way to do that.
Thanks.
Kyle:
I'm not a Javascript guy, but publishing your table in one service and then using Javascript API code in each client web map to query only the data from the table you want to display. One service would be easy on your ArcGIS Server and easy to maintain. See link, below.
Layer definitions on a dynamic map service | ArcGIS API for JavaScript
Thank you! My hunch was it was better to break it apart dynamically rather than have 50 separate services spooled up and the link was very helpful. I appreciate it.