EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB40349: What does the record of the DSSCSCONTENT History List table mean when the column SUB_ID = 256 in Microstrategy 9.x?


Community Admin

• Strategy


In a database-based History List, the column SUB_ID = 256 of the DSSCSCONTENT table means that a Report Services Document was sent to the History List. Therefore, a stream file (a file read or written sequentially) is created. 

In a database-based History List, the column SUB_ID = 256 of the DSSCSCONTENT table means that a Report Services Document was sent to the History List. Therefore, a stream file (a file read or written sequentially) is created. 
 
In a flat file based History List, a stream file gets created into the Inbox folder when a Report Service Document is sent to the History List. In the case of a database-based History List, when a Report Services Document is sent to the History List, the data corresponding to the Report Services Document History List gets saved in the DSSCSCONTENT table and the column SUB_ID value is defined as 256.
 
The DSSCSCONTENT table records which the column SUB_ID value is 256 should not be manually deleted because these records will be automatically deleted when the corresponding document History List message is deleted.
 
A list of the existing SUB_ID types in a DSSCSCONTENT table may be retrieved by running the following SQL statement using the Strategy DB Query Tool:
 
SELECT SUB_ID FROM DSSCSCONTENT GROUP BY SUB_ID;
 
The current SUB_ID types and its meanings are:

  • 1 (Result SQL)
  • 2 (Prompt Answers)
  • 16 (PDF)
  • 32 (Excel)
  • 64 (CSV)
  • 128 (Document HTML)
  • 256 (Document Streams)
  • 512 (Settings)
  • 1024 (Report Result Definition)
  • 2048 (Result Cache)
  • 4096 (Flash)
  • 8192 (Document Result Binary)
  • 16384 (Flash in PDF Container)

 
NOTES:
 
For further information about History List database tables, please, refer to the following Technical Notes:

  • KB32849: Database Based History List - Best Practices and Frequently Asked Questions
  • KB31677: What tables are stored in the History List repository used in Database Based History List in Strategy 9.x

 


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

June 9, 2017