Product: TIBCO Spotfire®
How to determine size of a specific analysis file from the TIBCO Spotfire application database or Action Logs database
This is one technique to help you determine the size of an analysis file by using the TIBCO Spotfire application database or the Action Logs database. This is not the amount of RAM required when the report is opened, but instead the size of the .dxp file itself as stored in the library. You can query the TIBCO Spotfire application database with a query like:
select CONTENT_SIZE from lib_items where ITEM_ID='<GUID of dxp file>'or
select CONTENT_SIZE from lib_items where TITLE='<dxp name>' and item_type='4f83cd47-71b5-11dd-050e-00100a64217d'Where <dxp name> is updated with the name of the analysis file and <GUID of dxp file> is updated with the unique GUID of the analysis file you are investigating.
select CONTENT_SIZE from lib_items where ITEM_ID='a5e48046-75b5-4f30-bc50-22a87fc218bc'or:
select CONTENT_SIZE from lib_items where TITLE='My Baseball dxp' and item_type='4f83cd47-71b5-11dd-050e-00100a64217d'
Alternatively, if the Action Logs are enabled (see references), you can run this query against the Action Log database to get the size of an analysis file which has been opened from the library:
select ARG3 AS analysissize from [dbo].[ACTIONLOG] where [LOG_CATEGORY]='library' AND [LOG_ACTION]='load_content' AND [ID2]='<Librarypath>';Where <Librarypath> is updated with the path to the analysis file you are investigating. For example:
select ARG3 AS analysissize from [dbo].[ACTIONLOG] where [LOG_CATEGORY]='library' AND [LOG_ACTION]='load_content' AND [ID2]='/Spotfire/Test_Java_Script';
Note: These sizes are recorded in bytes, so when you compare it against with the library size in the TIBCO Spotfire Analyst ensure to convert into Kilobytes/Megabytes as needed.
Disclaimer: The content of this article is for informational purposes only. The subject material may change in any new versions with no notice and there is no responsibility by TIBCO to maintain or support future access to this internal application content. Modification of any internal application content is not recommended and can lead to an unsupported configuration. It is not intended to be used "As Is" in a Production environment. Always test in a Development environment. Doc: Action logs and system monitoring