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

ten million rows of data in one service layer-rendering speed- tips,ideas

KennethPurcell

Hi Folks, we have 58 counties in california' and have data from each of the counties into a single dataset which consists of 10000000 rows in the SDE , Publishing as a feature service layer has proven to be impossible so far, what would be the best recommendation to go forward with hosting it in the enterprise, would it be to split the data up into 58 separate layers and publish that way. and/or is there a way to stich those layers into one dataset that would be quicker?

Najděte více příspěvků označených jako

Accepted answers

berniejconnors

It sounds like you have all the parcel data for California (a google search estimates 13 million parcels in California). Perhaps a Vector tile cache would be a good option. You should be able to refresh the vector tile cache easily when you get updates from the counties.

Bernie.

All comments

AngusHooper1

If the dataset is point geometry then a hosted feature layer can handle 10 million points without any dramas.

If each feature is a duplicate polygon of the county boundary then I'd suggest you re-think why you need to be storing that spatial information 10 million times.

George_Thompson

Are you receiving errors when publishing?

How are the resources on the RDBMS and Enterprise when publishing?

How often is the data changing?

What is the data (point / line / poly)?

berniejconnors

Bernie.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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