Property to set current schema in JDBC Adapter connection

This is precisely the issue I am encountering. On dev and test I can connect as user A, B, C, D and PROD but in prod it seems that user PROD is way too powerful which is why I cannot use it. Unfortunately this solution using synonyms is not that liked by my client as it is deemed as a last resort solution and I am being asked to find another solution which does not entail any change on db level since the DB is not managed by us which are managing only the middleware part.


Do they have specific concerns about synonyms beyond “don’t like” or “last resort?” IMO, changing the wM IS JDBC connection pool all the time is the more risky proposition.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.