The content database has been shrunk following an externalization, but still appears to be larger than expected.
There is often a subset of table objects containing large amount of data such as audit tables, which a user is previously unaware of. It may also be that the amount of data intended to be externalized has not been externalized due to unintended filters being applied.
Within a query editor scoped to the content database to be analyzed, execute the SQL procedure below, which will dump the space utilization for each table in the database.
sp_msforeachtable 'exec sp_spaceused [?]'
NOTE: The reserved column is the total space (data + index) used.
Below are some explanations if the following tables are large in size:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center