Post reply

Agent Error log

  • August 3, 2012 at 8:01 am

    #279224

    Hello,

    I cant access the old SQLServer agent error logs. Through SSMS neither through query

    xp_ReadErrorLog 2, 2, NULL, NULL

    Error is Unicode file expected.

    Is there any issue with sql or other?.

    Regards
    Durai Nagarajan

  • August 6, 2012 at 3:54 am

    #1521921

    I've has this same error when the file was too big. Opening it in Wordpad worked fine. Can you locate the file?

    :exclamation: "Be brave. Take risks. Nothing can substitute experience." :exclamation:

  • August 6, 2012 at 4:01 am

    #1521927

    is there a way to split it when exceeds some size or else we have to use only no of file in configuration?

    Regards
    Durai Nagarajan

  • August 6, 2012 at 4:06 am

    #1521928

    you can run the procedure

    sp_cycle_agent_errorlog

    At a certain point to create a new log file.

    We do this once a month to both the SQL and Agent logs.

  • August 6, 2012 at 4:07 am

    #1521929

    I don't know of a way of splitting the error log but you could force the creation of a new log file whenever you want.

    For example, once a week create a SQL job that executes 'EXEC sp_cycle_errorlog'

    This will create a new log file!

    :exclamation: "Be brave. Take risks. Nothing can substitute experience." :exclamation:

  • August 6, 2012 at 4:11 am

    #1521933

    thanks both

    Regards
    Durai Nagarajan

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

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