February 27, 2008 at 11:31 am
While attempting to use local synonyms that are defined for tables on a linked server testing works fine through the query tool. Some of the insert, update statements used by our application [MS Dynamics Great Plains] execute triggers defined on local tables that use the synonyms. Some of the time the trigger will generate an error message saying that the connection is not using ANSI_NULLS & ANSI_PADDING. I have set the TCP connection for SQL Server to use ANSI_NULLS,DEFAULTS,PADDING. Also the ODBC connection to Great Plains from the client has ANSI_NULLS,PADDING set. I checked the stored procedures that appear to be used at the time of the failure and recreated all of them to SET ANSI_NULLS ON
Does anyone have any suggestions on where else to set TCP connection settings? or how to control the connection from server one to server two. Both are SQL Servers so the default SQL Native Client is used for the linked server connection. Does the user session connection settings override the linked server connection settings?
Thank you for any assistance.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply