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

KB37830: How to obtain all messages for a specific user from a history list database in MicroStrategy 9.x


Community Admin

• Strategy


Using database History list users running Strategy 9.x are able to store a huge number of messages on the same repository. This is a great advantage of the Strategy product suite, however it may be difficult in some cases to get the entire history list database in-house to troubleshoot problems related to History list messages.
 
This technical note is intended to provide an alternative on how to create a subset of history list messages based on the user that created the message.  Refer to the following technical note for instructions on how to get specific messages from a History list database as well as the procedure to restore the repository.
 
KB31180: How to obtain specific messages from a history list database for troubleshooting in Strategy Intelligence Server 9.x
 
In order to get all history list messages created by a specific user, users may want to run the SQL statements shown below into the copy (empty) of the History List database that was created as per the instructions in KB31180. Do not attempt to run the INSERT statement against the original History List database.
 
 
SQL Statements
 
insert into dsscsmsginfo
SELECT * FROM .dsscsmsginfo
WHERE USER_ID='<GUID OF USER>'
 
insert into dsscscontent
SELECT * FROM .dsscscontent
WHERE CONTENT_ID IN (select message_id from dsscsmsginfo)
 
insert into dsscssysprop
SELECT * FROM .DSSCSSYSPROP;
 
 
Syntax of the above SQL statements should be adjusted by end users depending upon the specific database type.


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

June 12, 2017