Change journalling

Change journalling is only for maintaining logs for tracking changes in mstr objects. And mstr store these change logs in metadata tables. So these are purely just for log purpose no versioning is provided there.

How to enable/disable change journaling for a project?

The following procedure describes how administrators can enable or disable change 

journaling for all projects within a project source:

1.      In Desktop, log into a project source. The user logging in to Desktop must be granted the "Audit Change Journal" privilege.

2.      Expand Administration, and then expand System Monitors.

3.      Right-click Change Journal Transactions and select Manage Change Journal. 

4.      To enable or disable change journaling for this project source, select or clear the Enable change journaling check box.

5.      To enable or disable change journaling for all projects in the project source, select the Apply to all projects check box.

1.      If the desired action is to disable for all, but "Enable change journaling" is unchecked, 

2.      perform the following actions in this order:

a.              Check "Enable change journal" and "Apply to all projects".

b.              Click OK.

c.              Return to the Change Journal Manager.

d.              Uncheck "Enable change journal" and check "Apply to all projects"

e.              Click OK again. This will disable the change journaling for all projects if 

3.      "Enable change journaling" was not checked to begin with.

4.      Click OK. Change journaling should be enabled/disabled for each project,

depending on whether the option has been checked or unchecked.

TN34086: How to enable or disable change journaling for all projects within a project source in MicroStrategy 9.0.x

The following procedure describes how administrators can enable or disable change journaling for all projects within a project source:

1.    In Desktop, log into a project source. The user logging in to Desktop must be granted the "Audit Change Journal" privilege.

2.    Expand Administration, and then expand System Monitors.

3.    Right-click Change Journal Transactions and select Manage Change Journal. 

4.    To enable or disable change journaling for this project source, select or clear the Enable change journaling check box.

5.    To enable or disable change journaling for all projects in the project source, select the Apply to all projects check box.



If the desired action is to disable for all, but "Enable change journaling" is unchecked, perform the following actions in this order:

1.    Check "Enable change journal" and "Apply to all projects".

2.    Click OK.

3.    Return to the Change Journal Manager.

4.    Uncheck "Enable change journal" and check "Apply to all projects"

5.    Click OK again. This will disable the change journaling for all projects if "Enable change journaling" was not checked to begin with.

6.    Click OK. Change journaling should be enabled/disabled for each project, depending on whether the option has been checked or unchecked.

 TN34786: Administrator is only able to view Change Journal transactions for the current day in MicroStrategy Desktop 9.0.x

SYMPTOM:

When reviewing the Change Journal Transaction monitor, the Administrator user is only able to view entries  for the current day in MicroStrategy Desktop 9.0.x

CAUSE:

This is the default behavior. The out-of-the-box view filter for Change Journal Transactions is set to include the current day only.

ACTION:

Follow the next steps to edit the filter and display additional entries in the Change Journal Transaction monitor

1.    In MicroStrategy Desktop 9.0.x, right-click on Change Journal Transactions, and select the 'Filter' menu item.

2.    Edit the Time Range to view Change Journal Transactions for earlier dates as shown in the image below.

The table below contains a list of the MicroStrategy 9.0.x Change Journaling Transaction Type values and descriptions.

Transaction Type	Type Description
1	Enable Change Journal
2	Disable Change Journal
3	Purge Change Journal
4	Save Object
5	Save Objects
6	Save Link Items
7	Delete Object
8	Delete Objects
9	Delete Project
10	Copy Object
11	Merge User
12	Collect Garbage
13	Write System Property
14	Write Database Password

NOTE: Starting from 9.0.1, for Transaction Type the use of 4 (Save Object) and 7 (Delete Object) are obsolete. All object save and delete transactions, regardless of the number of objects changed, are recorded as 5 (Save Objects) and 8 (Delete Objects).

The table below contains a list of the MicroStrategy 9.0.x Change Journaling Change Type values and descriptions.

Change Type	Type Description
1	Create Object
2	Change Object
3	Delete Object
4	Touch Folder
5	Create Link Item
6	Change Link Item
7	Delete Link Item
8	Enable Change Journal
9	Disable Change Journal
10	Purge Change Journal

 TN209516: What are the "Next Transaction(s)"/"Previous Transaction(s)" buttons in the Change Journal Transactions monitor in MicroStrategy Desktop 9.0.x-9.4.0 and MicroStrategy Developer 9.4.1?

Note: For purposes of this tech note, any reference, either through text or screenshots, to MicroStrategy Desktop 9.0.x-9.4.0 will be referred to as MicroStrategy Developer, the name of the equivalent product offering in MicroStrategy 9.4.1.

Inside of the Change Journal Transactions monitor in MicroStrategy Developer (Project Source > Administration > System Monitors > Change Journal Transactions), there are two buttons that display in the first page (if the timeframe used for the filter is large enough), called "Next Transaction(s)" and "Next 1000 elements...", as shown:

The monitor explicitly displays each unique change element, not each unique transaction element. A single transaction can contain multiple changes. For instance, if a new folder is created, the transaction for creating the new folder contains two changes:

1.    Creation of the folder

2.    Modification of the parent folder

Because of this, a single transaction ID can span across multiple change elements in the monitor.

"Next Transaction(s)": This button displays the next most recent set of 1000 transactions, sorted by time. This can display a different number of change elements shown in the monitor and can span across multiple pages, the number of pages varying due to the number of average changes per transaction. Each transaction set displays 1000 unique transactions and all elements associated with those transactions. If there are multiple changes for each transaction, there will be multiple pages within a transaction set and can be browsed by using the "Next 1000 elements..." button summarized below.

"Next 1000 elements...": This button will display the next 1000 elements available within a transaction set. Each page of changes can only display a subset of the 1000 transactions recorded as there can be multiple changes inside of a single transaction. For instance, if each transaction that occurred within a specific timeframe contained 4 changes and the monitor was sorted by time, there would be 1000/4=250 unique transaction IDs on that page, and you would need to hit the "Next 1000 elements..." button to move to the next page of changes within the transaction set.