KB202534: Filtering history list messages by read status does not reflect any changes when the history list is hosted in SQL Server 2008 or 2012 databases in MicroStrategy 9.3.x - 9.4.x

SYMPTOM:
When hosting history list messages in either SQL Server 2008 or SQL Server 2012 database, filtering the messages by read status does not reflect any changes.
 
STEPS TO REPRODUCE:
This issue can be reproduced in Strategy version 9.3.x to 9.4.x using SQL Server 2008 database to host history list messages.

1. Create a SQL Server 2008 database and set it up as the History List database for Strategy Tutorial
2. Send a report to history list
3. Go to Administration > System Monitors > History List Messages, right click the new message and select "Mark as Read"
4. On the same page, filter by "Read" status as "No" (this should filter out the message just marked as "Read")
5. No changes are reflected

 
CAUSE: 
This is a known issue with Strategy 9.3.x to 9.4.x.
 
ACTION:
Contact Strategy Technical Support for an update on this issue.
 
WORKAROUND:
Use a different database to host history list messages such as Microsoft Access.
 
Additionally, filtering on read status works within the Projects History for SQL Server databases.
 
The downside to this method is the history list messages shown here are only the ones for the user currently logged in.  When viewing the history list messages within the System Monitors it is for all users in the metadata.