topic Geodatabases - How many to create? in Geodatabase Questions

Geodatabases - How many to create?

KenricMcCay — Wed, 12 Nov 2014 15:44:45 GMT

Hello,

I have approximately 60 shapefile I use. As of right now, they are all in one geodatabase. I was wondering if there is a rule of thumb for when to create a new geodatabae?

Within my one geodatabase, I have multiple feature classes that could be categorized into something completely different. For example, I have fiber optics within my geodatabase that also contains the downguy locations for utility poles.

Should I continue to keep everything in one geodatabase or start to create multiple ones and grouping the feature classes within those?

Thank you for your advice!

Re: Geodatabases - How many to create?

George_Thompson — Wed, 12 Nov 2014 16:13:35 GMT

Hi Kenric,

If you are using shapefiles, then they are stored outside of a geodatabase.

There is no "rule of thumb" for when to create a new geodatabase to store your data. It depends on many different factors (too many to list here).

Here are the limitations for both file geodatabases and enterprise geodatabases:

File geodatabase limitations

Enterprise geodatabase limitations

Hopefully this gives you a starting point to go from. Based on only having 60 feature classes, I would say that a single geodatabase should be fine at this time.

-George

Re: Geodatabases - How many to create?

KenricMcCay — Wed, 12 Nov 2014 16:16:24 GMT

Thank you for getting back to me quickly. I will look at this, but it seems like I am doing fine for now!

Re: Geodatabases - How many to create?

StevenGraf1 — Wed, 12 Nov 2014 16:34:56 GMT

If you have a bunch of related shapefiles, you could group them together inside a geodatabase using feature datasets. This way you can better organize your data while storing everything inside 1 geodatabase

Steven

Re: Geodatabases - How many to create?

VinceAngelo — Wed, 12 Nov 2014 18:41:50 GMT

Except that this is not recommended practice. Using feature datasets for "folder" organization hurts performance and makes simple feature classes much less simple.

- V

Re: Geodatabases - How many to create?

StevenGraf1 — Wed, 12 Nov 2014 18:59:21 GMT

How bad does it hurt performance? I'm thinking about this from an enterprise geodatabase. I put all my data inside feature datasets because its easier to manage permissions for 1 feature dataset rather than 50 feature classes. Maybe this is a topic for another discussion. Is their a best practice document out there for this?

Thanks,

Steven

Re: Geodatabases - How many to create?

VinceAngelo — Wed, 12 Nov 2014 19:42:15 GMT

As with all things GIS, the answer is "It depends." I have seen performance crippled by thousands of feature datasets with dozens of feature classes in each. Esri training classes make it quite clear that feature datasets exist for cooperative table management associated with geometric networks, topology, or feature linked annotation. It's a common theme in these discussion threads as well. I didn't find any specific "best practice document" but I did find this discussion in the old, old forums.

I would suggest that ease of administration should not be the goal in configuring geodatabases. Best practice for security in databases involves creating one or more database roles for each access paradigm needed ("browsers", "basemap editors", "primary data editors", etc), then granting the roles the appropriate permissions on the feature classes once, and granting users access to the roles. In this way, adding a new user is still simple (grant them the appropriate roles), and you don't need to tie your tables into a monolithic access block.

- V

Re: Geodatabases - How many to create?

StevenGraf1 — Wed, 12 Nov 2014 19:59:18 GMT

Thanks for the information.

Steven