MySQL - set transaction isolation level

Comments

4 comments

  • Avatar
    Andrew Block

    Michael what version of Sisense are you on?

  • Avatar
    Michael Pose

    Hello Andrew,

    we are on Version 6.5.2.10062

  • Avatar
    Andrew Block (Edited )

    You may want to verify with support but the issue we came across that was causing build increase (from 6.5 to 6.7) was a log file config and the amount of detail it was storing in the Prism Server logs.

    Again I would run this by your Customer Success Manager or support and see if they think this might be the same issue but I will still provide the step we did to fix it:

    1) Open this file directory - C:\ProgramData\Sisense\PrismServer\PrismServerLogs


    2) Open in notepad as an administrator (or with notepad++) and open the following file:

    ECS_LogConfig.10.XML

    3) Find the <priority value="trace" />

    4) Change the "trace" value to "info"
    5) Save
    6) Initiate the same build to monitor the new build time.

     

     

     

  • Avatar
    Michael Pose

    Ok, we can try that and see if that helps.

    But my initial question was also for some information about the transaction isolation level used by the MySQL data connector and what type of transaction it creates (if any). And also if those settings are configurable. I could not find that documented anywhere.

    Thanks again,

    Michael

Please sign in to leave a comment.