Login Auditing

  • Hi Techies.

    I have to audit the Login information on 10-12 Production Servers(most of them are SQL Server 2000), My requirement is to put all the Audit information in table.I have a Dedicated Monitoring Server(SQL Server 2005) for Auditing purpose , but this time i don't know the impact(in terms of Performance hit, Space). Can any one tell the impact if i run the profiler trace 24x7 to capture the Login information for all the Prod Servers.I will welcome your Comments, recommendations and suggestions to solve my purpose.

    Thanks in Advance.

  • We have a profiler trace running 24/7. But we only store information of SP's that take more than 250 Millisec. We do not see any perfomance issue on our DB because of that.

    -Roy

  • Thanks Roy

    But I am not concern about only database or one server , i would like to know about overall impact when i run trace for all servers before following this path.

    looking for all the other options to achieve my target.

    Regards

  • Are you worried about the impact on the monitoring server or the servers you are monitoring?

    Are you using server-side traces or profiler? If profiler, then the monitoring server & network will likely take a hit, but how much will depend on what you are capturing.



    Scott Duncan

    MARCUS. Why dost thou laugh? It fits not with this hour.
    TITUS. Why, I have not another tear to shed;
    --Titus Andronicus, William Shakespeare


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

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