Enterprise Geodatabase with 100K point features and 300K attachments?

[MichaelTorbett]

Good afternoon,

I'm considering a project that will involve using an Enterprise Geodatabase (Azure SQL Database) with over 100,000 point features and upwards of 3 attachments for each point over time.  This will undoubtedly make the database very large which gives me some concerns. This data for this database will be collected using Survey 123. 

Has anyone had experience managing an Enterprise Geodatabase of this size? If so, did you experience any performance issues?

Thanks,

Michael

[CodyPatterson]

Hey @MichaelTorbett 

This would definitely be an extremely large database depending on the size and type of the attachment, maybe upwards of multiple Terabytes on the high end of things. Our own database is of similar size.

The main issue you'll face is unindexed or unoptimized tables, you'll want to ensure that all your tables are indexed properly to reduce the amount of overhead your database will have during daily operations. Our Survey123 instance does not face a lot of latency or issues even though our database is very large, typically the thing that bogs down a database would be queries and processes running during the data transfer window, but you may not have a large issue with that if the biggest problem is just a large database.

tldr; I've had no issues with Survey123 on an indexed database of the size 4-10TB.

Cody

[MichaelTorbett]

Hey Cody,

Thank you for your input. This is very encouraging. Just curious, what type of database are you using and is it in the cloud?

[CodyPatterson]

Hey @MichaelTorbett 

We're currently using a Microsoft SQL Server database and it is all on-prem!

Cody