Connections DB wiped out

[tzimmerman]

I just downloaded and started 1.74.6023.15358 portable. I configured it to use SQLServer to store connections as I had all my connections stored in the database using the previous version (1.72). Initially I had an incorrect password. When I correct that and mRemoteNG started, it wiped out all of my connections.

Seems like this is a significant issue unless I did something I shouldn't have?

[Wee_Tommy]

Hi there.
I had exactly the same issue.
I use mremote on 3 different machines and they all seem to wipe the connections from time to time.
After the 2nd time i created a full set, then exported to a file, then can just quickly import them when it happens, but it is strange the way the machines wipe the connections out.
Hopefully the bugs will get ironed out as this is a really cool feature.

[dmsparer]

The Sql database feature was only ever released as a beta. To update the DB, the current code deletes all connections then recreates the whole list. If something interrupts this process, the DB can be left in an inconsistent state. We would eventually like to improve the DB feature, though there is currently no time table for doing so.

[tzimmerman]

This is what I suspected. Is it safe to assume that if I were to disable the "Save connections on exit" option, it would not wipe out and try to update my connections on exit? And therefore I would not lose any connection information if something were to happen during the exit process?

[dmsparer]

Yea, that should work.