I have changed camunda embedded h2 database by my sql server database in order to get rid of this error
but when i start work with sql server i got this exception:
here are several things i am interested in:
- as i have seen from camunda database it convert each instance data into bytearray and then saves this data in history tables, how should i prevent this process( i mean saving all data in histroy tables?)? in case data which i have received from service is huge, how can i save all this data inside camunda environment will i nee hisotry clean up or relative process?
2.i have seen this implementation https://github.com/camunda-consulting/code/tree/master/snippets/clean-up-history but it seems to work only on oracle, by the way do you know anything about history clean up implementation which works on sql server as well ?
- Can i use camunda inside updatting or adding it’s instance in HistoricVariableInstanceEntity, i mean does program uses this inctace later or it is just for monitoring?
- should i do any extra configuration on my camunda database ( i mean my sql server database) to increase size of instance?
@yana.vasileva you are always helpful to me, do you have any idea about it?