We have JDBC adapter 6.5 hitting a MS SQL Server. We have two issues. First issue is it seems like whenever we have network problems the polling notifications inexplicably gets disabled. When it gets disabled and we re enable it is when the second issue comes in. When we re enable it, a new DB trigger gets create that has a different name and when the .NET application writes to the notification table, the transaction fails. Anyone have a similar issue?
It is an explicit feature of the adapter connection to disable itself after a period of failures. I think you can control this but I’m not sure of the settings.
It is common practice to use basic notification instead of other notification types so that the DB trigger is not controlled by the adapter connection. Instead, manage the DB trigger via your normal DB processes.