You’re offline. This is a read only version of the page.
62
Hello,
We have a table in production that is taking up 11 GB of total size out of which data is 1 GB and index size is 10 GB (10x)! Since this is totally managed by Microsoft, we do not have any insight into why the indexes are taking ten times the size of the data held by the table. What we understood from Microsoft support is that...
These are all auto created indexes by Database Management system. In your case, this table is being used aggressively by applying various filters. Based on the filters you used in the views; respective SQL query will get generated. If that SQL query is performing slow, Database management system will create indexes based on the filter and sort conditions used in that query.
The challenge we are facing is that we do not have any insight into the indexes being created, the size of the individual indexes, and the queries or filter conditions that result in the creation of these indexes. How do we go about addressing this given this is a managed database? If this was SQL Server, we could have used a number of tools to identify the root-cause.
Btw, we turned off "Searchable" for a lot of columns but looks like it doesn't have any effect on the indexes.
Share
Report
All responses (
Answers (
