is it possible that replication generates 50 new procesess in a second?

  • Our IT complains that syslogs and security logs become enornous and hard to read because of

    the entries for process created and process exited with user name sqladmin on db server . Is there any way to find out what is causing so many processes to be created. I suspect that it is replication because there aren't that many jobs and they do not run every second. Maybe somebody had similar issues,

    LL

  • Does that username match the account that SQL agent runs as?

    Most of the replication jobs run continually, rather than frequently starting and stopping.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • the user name is always sqladmin

  • sorry, I didn't make myself clear, yes, this is the same account that runs replication

  • yes, replication is ran under slqadmin account

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply