SqlDependency raises an error in another application

I have a project where I need to track changes to a third party database.

SqlDependency is a good solution, but it throws the following error in a third party application.

INSERT error because the following SET parameters are incorrect settings: "ANSI_NULLS, QUOTED_IDENTIFIER, ANSI_PADDING". Confirm that SET parameters 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.

(The app works fine when my test program below doesn't work)

In which SET options does this apply?

The only operation I performed was ALTER DATABASE TestDb SET ENABLE_BROKER

to enable notifications.

I also did:

CREATE QUEUE ContactChangeMessages;

CREATE SERVICE ContactChangeNotifications
    ON QUEUE ContactChangeMessages
    ([http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification]);    

      

        
        
        
      

    

Here is my Linqpad test code that works great if I insert / update / delete records in management studio.

void Main() {
    const string cs = "Data Source=.;Initial Catalog=TestDb;Trusted_Connection=True";

    var are = new AutoResetEvent(false);
    using (var connection = new SqlConnection(cs)) {
        connection.Open();
        SqlDependency.Start(cs);
        using (var cmd = new SqlCommand()) {
        cmd.Connection = connection;
        cmd.CommandType = CommandType.Text;
        cmd.CommandText = "SELECT orderNo FROM dbo.Orders WHERE ProductNo = '111'";

            var dep = new SqlDependency(cmd, null, 60);
    dep.OnChange += (s,e) => { 
                Console.WriteLine(e.Info);
                are.Set();
            };
            using (var reader = cmd.ExecuteReader()) {
                while (reader.Read()) {
                }
            }
            are.WaitOne();
            SqlDependency.Stop(cs);
        }
    }
}

      

        
        
        
      

    

I don’t know and cannot change how the third part application connects to the database. I can run the sql profiler if more information is needed.