Return to Question

I have a Server level Audit running and informational messages are continuously placed in the SQL Error log (every hour):

02/06/2020 22:05:43,spid96,Unknown,Audit: Server Audit: 66026 Session has been closed 02/06/2020 22:05:43,spid96,Unknown,Audit: Server Audit: 66026 State changed from: STARTED to: SHUTTING_DOWN 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66026 Initialized and Assigned State: STARTED 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66026 Initialized and Assigned State: START_FAILED 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66025 Session has been closed 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66025 State changed from: STARTED to: SHUTTING_DOWN My question is, why does this happen and more important can this be prevented (while continuing the audit)?

I have a Server level Audit running and informational messages are continuously placed in the SQL Error log (every hour):

Audit: Server Audit: 65976, Initialized and Assigned State: STARTED Audit: Server Audit: 65976, Initialized and Assigned State: START_FAILED Audit: Server Audit: 65975 Session has been closed Audit: Server Audit: 65975, State changed from: STARTED to: SHUTTING_DOWN

My question is, why does this happen and more important can this be prevented (while continuing the audit)?

I have a Server level Audit running and informational messages are continuously placed in the SQL Error log (every hour):

Audit: Server Audit: 65976, Initialized and Assigned State: STARTED Audit: Server Audit: 65976, Initialized and Assigned State: START_FAILED Audit: Server Audit: 65975 Session has been closed Audit: Server Audit: 65975, State changed from: STARTED to: SHUTTING_DOWN

My question is, why does this happen and more important can this be prevented (while continuing the audit)?

I have a Server level Audit running and informational messages are continuously placed in the SQL Error log (every hour):

02/06/2020 22:05:43,spid96,Unknown,Audit: Server Audit: 66026 Session has been closed 02/06/2020 22:05:43,spid96,Unknown,Audit: Server Audit: 66026 State changed from: STARTED to: SHUTTING_DOWN 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66026 Initialized and Assigned State: STARTED 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66026 Initialized and Assigned State: START_FAILED 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66025 Session has been closed 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66025 State changed from: STARTED to: SHUTTING_DOWN My question is, why does this happen and more important can this be prevented (while continuing the audit)?

I have a Server level Audit running and informational messages are continuously placed in the SQL Error log (every hour):

02/06/2020 22:05:43,spid96,Unknown,Audit: Server Audit: 66026 Session has been closed 02/06/2020 22:05:43,spid96,Unknown,Audit: Server Audit: 66026 State changed from: STARTED to: SHUTTING_DOWN 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66026 Initialized and Assigned State: STARTED 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66026 Initialized and Assigned State: START_FAILED 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66025 Session has been closed 02/06/2020 21:17:55,spid72,Unknown,Audit: Server Audit: 66025 State changed from: STARTED to: SHUTTING_DOWN My question is, why does this happen and more important can this be prevented (while continuing the audit)?

I have a Server level Audit running and informational messages are continuously placed in the SQL Error log (every hour):

Audit: Server Audit: 65976, Initialized and Assigned State: STARTED Audit: Server Audit: 65976, Initialized and Assigned State: START_FAILED Audit: Server Audit: 65975 Session has been closed Audit: Server Audit: 65975, State changed from: STARTED to: SHUTTING_DOWN

My question is, why does this happen and more important can this be prevented (while continuing the audit)?