+11Hi all,
another question regarding MX_U table, if FSM application is in IFS managed service, who maintains the MX_U table for deleting the old records? As this table can be very big and the usage of old history might not be necessary anymore.
If it’s customer’s responsibility to maintain it, can you describe steps to check and do it?
Thanks again,
~Juni
Best answer by Hushan Hasarel
Hi Juni,
If it’s IFS managed, cloud services team can truncate the MX_U table. They can do it directly from the database itself. If customer does it, they can use the following query to truncate the table
TRUNCATE TABLE mx_u
If you want to just check the content,
SELECT * FROM mx_u
RnD has added a App Param called USAGE_DAYS_TO_SAVE where you can set the Default number of days to save usage data (MX_U) for perform_analyze_usage. This is available from update 16
Hope this helps.
Best Regards,
Hushan
+24Hi
The app param USAGE_DAYS_TO_SAVE controls how far back MX_U will save transactions for. Once that is set, refresh cache and the transactions will only be stored for that length of time.
To clear the table down entirely would need to be done by IFS Managed Cloud team and would be up to them to determine if required or not.
Kind regards,
Lee Pinchbeck
+12Hi Juni,
If it’s IFS managed, cloud services team can truncate the MX_U table. They can do it directly from the database itself. If customer does it, they can use the following query to truncate the table
TRUNCATE TABLE mx_u
If you want to just check the content,
SELECT * FROM mx_u
RnD has added a App Param called USAGE_DAYS_TO_SAVE where you can set the Default number of days to save usage data (MX_U) for perform_analyze_usage. This is available from update 16
Hope this helps.
Best Regards,
Hushan
+11
thank you for your replies.
We have FSM6U14. And the app params USAGE_DAYS_TO_SAVE exists. In the value it is set 14, I see 1st data now is from 4 Feb, 2022.
Best regards,
~Juni.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.