Is there any reason not to enable indexing on enterprise geodatabases?

[MDB_GIS]

By default, the option is off. I'd like to cut it on because it would be nice to be able to use the search function in enterprise geodatabases. But I wasn't sure if there was a reason it was off by default. I don't want to enable it, forget I did it and then find out about some weird issue caused by it a few months from now! Thank you for any information you can provide. 

[MarceloMarques]

Yes, you can enable this in the ArcGIS Pro document, read more in the post below.

Solved: ArcGIS Pro Search capability - Esri Community

The contents of enterprise geodatabases aren't indexed by default in ArcGIS Pro. To enable indexing, go to the Settings page (click Project tab in a project), click Options on the left, and click the Indexing option. In the Options dialog box, uncheck the box that says Skip enterprise database connections. Same thing for network folders--except you have to check the box to index them. Index project items 

Note, you still need to have the Database Administrator to rebuild indexes and gather new statistics for the Enterprise Geodatabase Database (Oracle, SQL Server, PostgreSQL) regularly, the above is only to index content in the ArcGIS Pro document for the search capability.

[MDB_GIS]

My options look a bit different than that. 

Either way, though, I was aware of the location. My primary question is if there is any reason I SHOULDN'T enable. Since it is disabled by default, I figured that there must be a reason. I just wanted to make sure there weren't any potential performance issues that could result from having it enabled. 

[MarceloMarques · Accepted solution]

if your enterprise geodatabase is quite large with many featureclasses and tables and if your map document has data from multiple enterprise geodatabases that are quite large, then you see, if you enable the Pro document index option for enterprise geodatabases it can have a performance impact to build the index and to maintain the index.

[MDB_GIS]

What would be considered large? I have two eGDBs with probably ~150 feature classes between both of them. All of them hold datasets at the county level. Nothing globe spanning. 

[MarceloMarques]

Pretty small, 150 featureclasses, shall have no impact if you enable Pro Document Index Search for geodatabases, something large will be in the order of thousands of featureclasses in the enterprise geodatabases all together, then probably you will not want you Pro document wasting time to index that for the search capability.

[MDB_GIS]

Perfect! I'll keep it enabled then! Makes life much easier being able to search for things!