MySQL - set transaction isolation level

Follow

Michael Pose

November 09, 2017 22:22

What transaction isolation level is being used by the Sisense connector? We are running into issues with longer running Elasticube builds. 

So we're trying to see if/how the transaction isolation level can be changed to "READ COMMITTED".
Also is there any auto-commit setting used by the MySQL data connector?

Thanks!

Michael 

0

• 

  Andrew Block December 05, 2017 19:08

  Michael what version of Sisense are you on?

  0

  Comment actions Permalink
• 

  Michael Pose December 05, 2017 19:12

  Hello Andrew,

  we are on Version 6.5.2.10062

  0

  Comment actions Permalink
• 

  Andrew Block December 05, 2017 19:26 (Edited December 05, 2017 19:26)

  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.

   

   

   

  0

  Comment actions Permalink
• 

  Michael Pose December 05, 2017 19:30

  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

  0

  Comment actions Permalink

Please sign in to leave a comment.