Multiple GDBs vs Single GDB

[mpboyle]

Our production enterprise system is currently 1 sde gdb (Sql Server 2014) with several (45 to be exact) datasets and 9 editable versions (based on department). The sheer number of datasets makes it a little cumbersome for users to find what they may be searching for.

I was wondering if anyone has tried breaking down a large sde gdb into several smaller gdbs, perhaps 1 sde gdb per department?  If so, is there is a performance advantage of having 1 large sde gdb versus several smaller sde gdbs?  Is response time better for smaller gdb versus larger gdbs?  Would reducing the number of versions have a benefit on performance?

I'm hoping to get some pros / cons of having 1 large sde gdb which is like a one-stop-shop for any GIS needs or several smaller sde gdbs meant for departmental needs.

Thanks!

[MichaelSmith1]

SDE on a scalable database should never become 'unworkable'.  You may need to change tuning parameters, but it's not a limitation in SDE or your database.  Trust me, there are way bigger databases out there.

[TheodoreF]

Regarding File Geodatabases in ArcGIS Pro, is there a performance benefit from splitting one large FGDB into multiple FGDBs?

Let's say the dataset is purely vector features. And lots of them!

Theo

[VinceAngelo]

Please ask new questions in a new thread.  "Lots" should be quantified, with more details on how the data is organized and being used.

- V