Dataset size remains same even in disabled "Query caching and Aggregation Training" State

[Kandarp]

I had a report that was set to run in direct query mode. During that time, I enabled the "Schedule Refresh and Performance Optimization" option along with Query Caching in the dataset to enhance the report's performance by speeding up data retrieval.

Additionally, I enabled Automatic Aggregations Training. As a result of these settings, data was cached in the dataset, and the report size increased to approximately 1500MB.

Recently, I switched my report from direct query to import mode. Consequently, I no longer require any query caching, so I disabled all the aforementioned options that were enabled during direct query mode to optimize performance.

However, even after a few days, the dataset size remains the same (1500MB) while my .pbix file is around 200MB. I anticipated that disabling the caching options would reduce the dataset size, but it still shows around 1500MB.

Please note that I can not delete existing file or dataset because new one will get published with new IDs which will create issues.

I'm wondering if this persistent size is due to the caching that occurred during the previous direct query mode. How can I reduce or eliminate this unnecessary caching and ultimately reduce the dataset's size? Any insights or suggestions would be greatly appreciated.

[amitchandak]

@Kandarp , Removed the published file and publish it again, or publish as a new file and check

[Kandarp]

Thanks @amitchandak for the quick response. 

By removing existing file and publishing it again will give me new report id and dataset id which I do not want. 

Is there any way that with the same IDs or Configuration I can achieve this. 

Thanks.