Technical Articles
Filestore analysis / Cleaning – which file belongs to which report
Are the file stores eating up all your resources and you don’t know which reports are causing it?
BI 4.1 SP7 Windows installation
Well you can analyze it via tools like TreeSize Free. A simple tool to order the files/folders by GB. You will see the analysis of your file store folder. The neat thing is you can drill trough the biggest folders into the file that is loaded with large sets of data. The problem is that you still know nothing, I explain in this blog how to know which document is linked with which file.
In the output file you will retrieve the instances and in the input file you’ll have your report/documents holding large sets of data.
FILESTORE:
- OUTPUT instances of reports control them by setting limits in CMC
- INPUT data of saved reports purge reportdata
The output files can be limited in the CMC and the input files should be purged.
But always check with the owners of the reports before handling!
But how do we know what is what?
Well by clicking through all the folders, you ‘ll find the file containing large sets of data. Right click on it select properties and copy the name.
go to your query builder
BOServer:port/AdminTools
and use
SELECT * FROM CI_INFOOBJECTS WHERE SI_FILES.SI_FILE1 = 'paste filename'
or
SELECT SI_GUID, SI_NAME FROM CI_INFOOBJECTS WHERE SI_FILES.SI_FILE1 = 'paste filename'
submit the query and in the outcome you can retrieve the CUID and name of the report.
*CUID thanks Former Member
LOGON as administrator in the SAP BI Launchpad and search for the name of the report (as admin you will see reports saved by users in their favourites as well)
Because the reportnames can be confusing, double check via CUID
QUERY RESULT REPORT PROPERTIES
check the guid of the report to match correct report->
Now you know which report is causing all your problems and you can take the necessary measures.
Happy cleaning!
Hi Koen, nice post! I think you mean check the CUID, not GUID. 🙂
Hi I was working on some CRM data, my bad!