After upgrading to version 6.5.3 from version 6.0, Other Activity still displays under the SQL Statement column from the History section
Third Party Applications run on scheduled times such as Replication Monitor or Snapshot Agent History Connection.
Snapshot replication is done together by SQL Server and Windows OS, this particular replication activity must be generating internal SQL activity but no explicit SQL statements. PA while scanning DB shared memory detects that there is SQL activity but does not find the associated SQL Handle object and since PA cannot categorize such activity to any actual SQL statement(s) or sessions, it will end up in Other Activity.
WORKAROUND
Unfortunately, there is no action to be taken to reduce this. Verify the Programs tab periodically and check Other Activity contributor programs.
RESOLUTION
Waiting for a fix in a future release of Performance Analysis for SQL Server.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center