HI All,
I just had an issue and was wondering if anyone else encountered.
I had sql server auditing enabled for updates to a specific table in a user table. the audit was writing the changes to a text file.
when I issued the command (ALTER SERVER AUDIT [Audit-20161007-112337] WITH (STATE = OFF)) the users on the front end started to experience blocking. the spid for the disable auditing command was blocked by spid 1. I couldn't\wouldn't kill spid 1 so I was left with no choice to bounce the instance.
the version of sql is sql server 2008r2 enterprise edition.
has anyone ever experienced anything similar? I don't see any bugs related to this .
Regards,
Niall
I just had an issue and was wondering if anyone else encountered.
I had sql server auditing enabled for updates to a specific table in a user table. the audit was writing the changes to a text file.
when I issued the command (ALTER SERVER AUDIT [Audit-20161007-112337] WITH (STATE = OFF)) the users on the front end started to experience blocking. the spid for the disable auditing command was blocked by spid 1. I couldn't\wouldn't kill spid 1 so I was left with no choice to bounce the instance.
the version of sql is sql server 2008r2 enterprise edition.
has anyone ever experienced anything similar? I don't see any bugs related to this .
Regards,
Niall
