Not sure what might've changed on foreign server's side, but now getting the below error when mapping foreign tables to any new views on the foreign server (actual server name altered for obv reasons. Connections to older views still work just fine). Is there any way to set those system variables to ON specifically as part of the SELECT that is taking place through the extension?
NOTICE: DB-Library notice: Msg #: 1934, Msg state: 1, Msg: SELECT failed because the following SET options have incorrect settings: 'ANSI_NULLS, QUOTED_IDENTIFIER, CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS, ANSI_PADDING'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations., Server: XXXXX-XXXXXX-XXXX, Process: , Line: 1, Level: 16
Not sure what might've changed on foreign server's side, but now getting the below error when mapping foreign tables to any new views on the foreign server (actual server name altered for obv reasons. Connections to older views still work just fine). Is there any way to set those system variables to ON specifically as part of the SELECT that is taking place through the extension?
NOTICE: DB-Library notice: Msg #: 1934, Msg state: 1, Msg: SELECT failed because the following SET options have incorrect settings: 'ANSI_NULLS, QUOTED_IDENTIFIER, CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS, ANSI_PADDING'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations., Server: XXXXX-XXXXXX-XXXX, Process: , Line: 1, Level: 16