What is the maximum number of tables/feature classes for an Enterprise GDB? Is there a similar reference for ArcSDE using SQL Server? http://resources.arcgis.com/en/help/main/10.2/index.html#//018s00000002000000 This is from Microsoft: https://technet.microsoft.com/en-us/library/aa933149%28v=sql.80%29.aspx Thanks!
Yes, we have over 100k tables based on an implementation mainly due to security requirements (no row level security). It takes a long time to connect to GDB and it does not fully compress. We are in the process of migrating to a more manageable number of tables and implementing an SOI to secure GIS services. I need to know if there are any published or non-published limits to the number of GDB objects. I was hoping this may help us determine before we hit the threshold or if we have already passed it. Thanks.
None that I know of. Had a user on a beefy box with 100k tables -- took 20-25 minutes to log in.
Databases are about rows, not tables. The tables should be kept as few as possible to prevent the high cost of inventory queries on the catalog.
- V
Thanks for your reply. Is there any online reference to maximum "usable" limits? At what limit will people run into problems? Thanks!
The system would be unusable long before you hit the table maximums (5.0e+05 tables, vice 2.1e+10 limit), so it doesn't really much matter.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.