Once the B_INDEX_ROWID parameter is customized to a different filegroup in the DBTUNE table, the feature class table and its indexes are stored in the same FileGroup.
Last Published: August 28, 2017ArcGIS for Desktop
Bug ID Number
BUG-000106806
Submitted
July 24, 2017
Last Modified
June 5, 2024
Applies to
ArcGIS for Desktop
Version found
N/A
Status
Known Limit
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
Additional Information
If you put a clustered index on a table then the data is stored where you tell the clustered index to be. This is because a clustered index IS the data. The actual table data is contained in the data pages of the clustered index.
A nonpartitioned clustered index and the base table always reside in the same filegroup.
https://technet.microsoft.com/en-us/library/ms190433(v=sql.105).aspx
Since the table is effectively moved to the same filegroup as the clustered index, any additional non-clustered index created on the table will reside on the same filegroup unless a different filegroup is specified.