quicksight spice Capacity not released

If you've deleted a dataset in Amazon QuickSight but still see it in SPICE (Super-fast, Parallel, In-memory Calculation Engine), and the capacity is not released, here are some steps you can take to address this issue:

Check Deletion Status: Ensure that the dataset has been properly deleted from Amazon QuickSight. Sometimes, deletion processes can take time to propagate fully. Revisit the QuickSight console and confirm that the dataset is indeed deleted. Verify SPICE Data Refresh: SPICE retains data for a certain period even after dataset deletion for caching and performance reasons. SPICE can take some time to refresh and reflect the changes made to datasets. Wait for some time and check if the deleted dataset is still present in SPICE. Purge SPICE Cache: If the deleted dataset persists in SPICE even after some time, you can try purging the SPICE cache. This can be done through the QuickSight console. Navigate to the QuickSight console, select the SPICE capacity management page, and look for options related to refreshing or purging the cache. Review SPICE Capacity: Keep an eye on your SPICE capacity usage. If the dataset is still taking up capacity after deletion, it could be a caching issue. Consider Data Source Permissions: Double-check the permissions and access settings related to the data source and datasets in both QuickSight and SPICE. Incorrect permissions might cause unexpected behavior even after deletion.

By following these steps and, if necessary, reaching out to AWS Support, you should be able to resolve the issue of the deleted dataset still appearing in SPICE and the associated capacity not being released.

Ismael Murillo