August 31, 2017 at 2:36 am
Hi,
in our Windows Event Viewer the "Application" log contains an huge number of informational data regarding data collector processes, I guess (see image in attachment). The origin is SQLISPackage120 e the event id is 12288. Here some events description:
- Package "QueryActivityUpload" started
- Package "TSQLQueryUpload" finished successfully
- Package "PerfCountersUpload" started
- Package "Set_{B83A3832-37CD-4C7A-88F6-6696DA5A7E43}_Master_Package_Upload" finished successfully
I could not find how to avoid this logs go to my Windows Event Viewer. Anyone has a solution?
Thanks.
Davide
August 31, 2017 at 4:09 am
Hi,
Why would you want to stop this from logging to the APPLICATION LOG. Is it causing an issue.
It is just logging the execution of some SSIS package. May help in the future if the package has a problem.
September 1, 2017 at 12:44 am
Hi Super Cat,
thanks for your reply.
I want to exclude only the "information" logs because the event viewer is full of this needless lines . In case the package has a problem I think it generates a "warning" or "error" log.Davide
September 1, 2017 at 2:41 am
Powershell might be your best bet to view the log and omit the event ID where it triggers an information message for the package or packages. Doesn't resolve the issue but you can read the log without the SSIS package information.
I think this maybe one for the POWERSHELL forums. Those whizz kids would be able to get something for you. This is more of a WINDOWS thing than SQL in my eyes.
September 1, 2017 at 7:29 am
secme - Friday, September 1, 2017 12:44 AMHi Super Cat,
thanks for your reply.
I want to exclude only the "information" logs because the event viewer is full of this needless lines . In case the package has a problem I think it generates a "warning" or "error" log.Davide
Why not just filter the event logs? You can filter by event id, source, event level, etc. In event viewer, right click on the log and select Filter Current Log.
Sue
September 1, 2017 at 7:49 am
Hi Sue
from my understanding, He wants to view all the events and not the SSIS ones. I don't use this every day but doesn't it just filter on what your are looking for rather than what you don't want to see.
September 1, 2017 at 7:58 am
Super Cat - Friday, September 1, 2017 7:49 AMHi Sue
from my understanding, He wants to view all the events and not the SSIS ones. I don't use this every day but doesn't it just filter on what your are looking for rather than what you don't want to see.
No, not necessarily. A couple of ways to exclude would include:
To remove an event id in the filtering - you prefix the number with a minus sign.
To remove an event source in the filtering, you select <All event sources> in the drop down and then scroll through the list and remove the one you don't want to view.
Sue
September 1, 2017 at 11:48 am
A registry change is required to prevent those.
Look at https://docs.microsoft.com/en-us/sql/integration-services/install-windows/install-integration-services
By default, in a new installation, Integration Services is configured not to log events that are related to the running of packages to the Application event log. This setting prevents too many event log entries when you use the Data Collector feature of SQL Server 2017. The events that are not logged are EventID 12288, "Package started," and EventID 12289, "Package finished successfully." To log these events to the Application event log, open the registry for editing. Then, in the registry, locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\130\SSIS node, and change the DWORD value of the LogPackageExecutionToEventLog setting from 0 to 1.?
this is for current version - for older versions the default was to log always.
you will search for the entry specific to your version of SQL Server
September 2, 2017 at 8:49 am
Thank you all!
federico_fonseca your solution is what i was looking for. So in SQL Server 2017 the default is to log only error events while in previous version I need to change a registry key if I want to obtain the same behaviour.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply