Ok. This is what I have experienced so far after the upgrade:

1: Most SSH keys were gone!
For some reason only 2 out of 14 keys were left after upgrade?!
I liked the idea of having the keys as part of VisualCron, but this is obviously not fully implemented yet.
Very tedious to modify 50 some connections using those keys. (It is not possible to see in Manage Connections if private key is used and rather annoying that the Manage Connections list is reloaded at [OK], so you have to dig down every time.)

2: SQL server task with multiple SQL's only work if "Split and run"-check-box is unchecked.
We only had a few of these but still a strange thing. In Oracle connections the check-box works normally.

3: SQL server connections now need to have "local login" to work it seems.

Still not able to test proxy within a connection.


VisualCron: please test your new versions better!

Ok. This is what I have experienced so far after the upgrade:

1: Most SSH keys were gone!
For some reason only 2 out of 14 keys were left after upgrade?!
I liked the idea of having the keys as part of VisualCron, but this is obviously not fully implemented yet.
Very tedious to modify 50 some connections using those keys. (It is not possible to see in Manage Connections if private key is used and rather annoying that the Manage Connections list is reloaded at [OK], so you have to dig down every time.)

2: SQL server task with multiple SQL's only work if "Split and run"-check-box is unchecked.
We only had a few of these but still a strange thing. In Oracle connections the check-box works normally.

3: SQL server connections now need to have "local login" to work it seems.

Still not able to test proxy within a connection.


VisualCron: please test your new versions better!

Hi,

1. We've been having a hard time reproducing this. We did test this. Do you happen to have any backup/export with those 14 keys you could send to us so we can see if we can reproduce it with your backup? If so, please send to support@visualcron.com

2. Could you give us an example of a query we could run/reproduce from here on this?

3. Yes, this is also intended.

---

Referring to #3 in the question and answer above, why?

We currently use domain logins, as we have several SQL servers we connect to. The local login has posed a production issue now. Is there a way around it? We need to be able to fix this ASAP, as there is time sensitive items that need to be processed.

Thank you!

Hi hjohnson

You can still use domian logins. Local login is about how you configure the VisualCron credential you use. It is not about SQL Server authenticated logins (database users).

If you open a Windows credential in VisualCron, you are able to tick "Local login" and "Load user profile".

After the last update you have to have these ticked to make the credential work against a SQL Server database (I'm not entirely sure about the Load user profile - try it out).

See: https://www.visualcron.c...doc/html/credentials.htm