Is there a way to make history engine write in history once per execution?I mean if I have a file with 10 000 updates I would prefere to write them in history in one file instead of creating 10 000 files with 1 update each !?!?
Also…I opened two instances of SQLNav on the same database connection . In one instance I was executing a file with 58 000 updates. In the other instance I was trying to execute few updates on other table. Well the second instance stopped working and SQLNav shuted down. My guess is that writing in history is not concurential (probably the second instance tryed to create a history file with the same name the other instance was doing this so one of them died, lucky for me it was the one with only few updates).
Also, in older versions there was a posibility to disable writing in history. Is there still such thing? Cause I don’t seem to find it.