Hi @StephanieWormit ,
I’m sorry to hear that you encounter this problem. The reason for this behavior is that the new DB Connector node and the Database Connector (Deprecated) node use different settings to register a JDBC driver. When we deprecated the old database nodes we also removed the preference page for this framework to prevent confusion when working with the new framework. However you can still register JDBC drivers for the deprecated framework manually by following the instruction from this post.
I know it is time consuming to update existing database workflow and the workflow migration tool can help only so much but is there anything else e.g. a missing feature that prevents you from updating to the new DB framework?
Bye
Tobias